Determining a security state designation for a computing device based on a source of software

ABSTRACT

For increased security, a source is determined for software to be installed on a computing device. In one approach, an application identifier is received from the computing device for an application to be installed. A source identifier of the application is determined. The application identifier and the source identifier are sent over a network to a server. A first state designation for the first application is received from the server. The first state designation represents a trusted state or an untrusted state. In response to receiving the first state designation, a second state designation is set. The second state designation is sent to the computing device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application of U.S. patentapplication Ser. No. 15/909,796, filed Mar. 1, 2018, and entitled“DETERMINING SOURCE OF SIDE-LOADED SOFTWARE USING AN ADMINISTRATORSERVER”, which is a continuation application of U.S. patent applicationSer. No. 15/427,491, filed Feb. 8, 2017, now U.S. Pat. No. 9,940,454,issued on Apr. 10, 2018 entitled “DETERMINING SOURCE OF SIDE-LOADEDSOFTWARE USING SIGNATURE OF AUTHORSHIP”, which is a continuationapplication of U.S. patent application Ser. No. 14/731,273, filed Jun.4, 2015, now U.S. Pat. No. 9,589,129, issued on Mar. 7, 2017, andentitled “DETERMINING SOURCE OF SIDE-LOADED SOFTWARE”, which claimspriority to U.S. Provisional Application Ser. No. 62/156,026, filed May1, 2015, entitled “DETERMINING SOURCE OF SIDE-LOADED SOFTWARE,” byRichardson et al., the entire contents of which applications areincorporated by reference as if fully set forth herein.

The present application is related to U.S. Non-Provisional applicationSer. No. 14/105,950, filed Dec. 13, 2013, entitled “ASSESSINGAPPLICATION AUTHENTICITY AND PERFORMING AN ACTION IN RESPONSE TO ANEVALUATION RESULT,” the entire contents of which application is herebyincorporated by reference as if fully set forth herein.

The present application is related to U.S. Non-Provisional applicationSer. No. 14/301,007, filed Jun. 10, 2014, entitled “MONITORING FORFRAUDULENT OR HARMFUL BEHAVIOR IN APPLICATIONS BEING INSTALLED ON USERDEVICES,” the entire contents of which application is herebyincorporated by reference as if fully set forth herein.

The present application is related to U.S. Non-Provisional applicationSer. No. 14/253,702, filed Apr. 15, 2014, entitled “MONITORING INSTALLEDAPPLICATIONS ON USER DEVICES,” the entire contents of which applicationis hereby incorporated by reference as if fully set forth herein.

The present application is related to U.S. Non-Provisional applicationSer. No. 14/253,739, filed Apr. 15, 2014, entitled “IDENTIFYING MANNEROF USAGE FOR SOFTWARE ASSETS IN APPLICATIONS ON USER DEVICES,” theentire contents of which application is hereby incorporated by referenceas if fully set forth herein.

The present application is related to U.S. Non-Provisional applicationSer. No. 13/786,210, filed Mar. 5, 2013, entitled “EXPRESSING INTENT TOCONTROL BEHAVIOR OF APPLICATION COMPONENTS,” by Wyatt et al., U.S.Non-Provisional application Ser. No. 13/692,806, filed Dec. 3, 2012,entitled “COMPONENT ANALYSIS OF SOFTWARE APPLICATIONS ON COMPUTINGDEVICES,” by Wyatt et al., and U.S. Provisional Application Ser. No.61/655,822, filed Jun. 5, 2012, entitled “EXPRESSING INTENT TO CONTROLBEHAVIOR OF APPLICATION COMPONENTS,” by Halliday et al., the entirecontents of which applications are hereby incorporated by reference asif fully set forth herein.

FIELD OF THE TECHNOLOGY

At least some embodiments disclosed herein relate to determining asource of software in general (e.g., software that is loaded onto orotherwise provided to a computing device), and more particularly, butnot limited to determining a source of applications or other softwareobtained by a computing device (e.g., an Android mobile device) over anetwork, via a connection to another device, or otherwise.

BACKGROUND

Mobile application management (MAM) relates to software and services forprovisioning and controlling access to internally developed andcommercially available mobile apps used in business settings on bothcompany-provided and “bring your own” smartphones and tablet computers.

Enterprise mobile application management is increasingly important dueto the widespread adoption and use of mobile applications in businesssettings. The “bring your own device” (BYOD) phenomenon makes mobileapplication management more important, with personal PC, smartphone andtablet use in business settings (vs. business-owned devices)significantly increasing. Mobile application management enablescorporate IT staff to download required applications, control access tobusiness data, and remove locally-cached business data from the deviceif it is lost, or when its owner no longer works with the company. Agrowing demand for mobile apps from employees is prompting organizationsto broaden beyond mobile device management to managing a growing numberof mobile applications.

An end-to-end MAM solution can provide the ability to control theprovisioning, updating and removal of mobile applications via anenterprise app store, monitor application performance and usage, andremotely wipe data from managed applications.

Mobile device management (MDM) is an industry term for theadministration of mobile devices, such as smartphones, tablets, laptopsand desktop computers. MDM is usually implemented with the use of athird party product that has management features for particular vendorsof mobile devices. For example, Good Technology provides MDM software.

MDM functionality can include over-the-air distribution of applications,data and configuration settings for all types of mobile devices,including mobile phones, smartphones, tablet computers, mobile printers,mobile POS devices, etc. Most recently laptops and desktops have beenadded to the list of systems supported. MDM tools are used for bothcompany-owned and employee-owned (BYOD) devices across the enterprise ormobile devices owned by consumers. Consumer demand for BYOD is nowrequiring a greater effort for MDM and increased security for both thedevices and the enterprise to which they connect. By controlling andprotecting the data and configuration settings for all mobile devices ina network, MDM can reduce support costs and business risks.

With mobile devices becoming commonplace and increased numbers ofapplications becoming available for mobile devices, mobile monitoring isgrowing in importance. Numerous vendors help mobile devicemanufacturers, content portals and developers test and monitor thedelivery of their mobile applications. This testing is done in real-timeby simulating the action of thousands of customers and detecting andcorrecting bugs in the applications.

Typical solutions include a server component, which sends out themanagement commands to the mobile devices, and a client component, whichruns on the mobile device and implements the management commands.

Central remote management uses commands sent over the air to mobiledevice handsets. An administrator at a mobile operator, an enterprise ITdata center or a handset OEM can use an administrative console to updateor configure any one handset, group or groups of handsets. The OpenMobile Alliance (OMA) has specified a platform-independent devicemanagement protocol called OMA Device Management. It is supported byseveral mobile devices, such as PDAs and mobile phones.

Over-the-air programming (OTA) capabilities are a component of mobilenetwork operator and enterprise-grade mobile device management software.These include the ability to remotely configure a single mobile device,an entire fleet of mobile devices or any IT-defined set of mobiledevices; send software and OS updates; remotely lock and wipe a device;and do remote troubleshooting. OTA commands are sent as binary messages,which are messages including binary data.

Mobile device management software enables corporate IT departments tomanage the many mobile devices used across the enterprise; consequently,over-the-air capabilities are in high demand. Enterprises using OTA aspart of their MDM infrastructure demand high quality in the sending ofOTA messages. Present day MDM solutions offer both Software as a Service(SaaS) and on-premises models.

As mentioned above, one example of mobile device management software isprovided by Good Technology which provides some degree of control andvisibility for an administrator of mobile devices. IT managers ensurethat mobile devices comply with their organization-specific IT policiesand that the correct configuration is pushed to devices. Good's mobiledevice management software permits users to self-enroll over-the-air. Inaddition to automatically configuring corporate policies and controls,IT can automatically setup WiFi, VPN and Exchange ActiveSyncconfigurations on mobile devices.

An administrator (admin) defines and deploys policies for anorganization. The admin may choose from a set of policy controls overpassword, device encryption, camera, Wi-Fi, VPN, etc. If a device islost, stolen, retired or replaced, the admin can wipe data from thedevice to reduce the chance of data loss.

The admin can control and manage various devices from a single console.Good's MDM supports a wide array of mobile devices, operating systemsand technologies including Apple iOS, Apple Watch, Android, Windows Pro,Window Phone and Samsung KNOX. Whether Bring Your Own Device (BYOD),Corporate-Owned, Personally-Enabled (COPE) devices or a combination ofboth are utilized, customizable policies ensure the right policies areapplied to the right device.

Good's MDM supports use cases including business users, remote workers,highly-sensitive users, shared devices, and kiosks. Good's MDM can bedeployed using a fully cloud-based deployment. Good's MDM can be fullyintegrated with Good Technology's Dynamics Secure Mobility Platform.

As users of mobile devices desire to and are able to installapplications from numerous various sources that are beyond the controlof an administrator, there is an increased risk that malware or otherundesirable software may be installed. One source of software availableto users, that may be beyond the control of or monitoring byadministrators, is peer-to-peer file sharing (e.g., using the BitTorrentprotocol). In some cases, certain file sharing sources may be untrustedor even a known bad source of software loaded onto mobile devices.

BitTorrent is a protocol for peer-to-peer file sharing used todistribute large amounts of data over the Internet. BitTorrent is one ofthe most common protocols for transferring large files. To send orreceive files, a user must have a BitTorrent client (a computer programthat implements the BitTorrent protocol).

Some popular BitTorrent clients include Xunlei, Transmission, μTorrent,MediaGet, Vuze and BitComet. BitTorrent trackers provide a list of filesavailable for transfer, and assist in transferring and reconstructingthe files. BitTorrent clients are available for a variety of computingplatforms and operating systems including an official client released byBitTorrent, Inc. As of January 2012, BitTorrent is utilized by 150million active users according to BitTorrent, Inc.

The BitTorrent protocol provides no way to index torrent files. As aresult, a comparatively small number of websites have hosted a largemajority of torrents, many linking to copyrighted material without theauthorization of copyright holders. There is controversy over the use ofBitTorrent. BitTorrent metafiles themselves do not store file contents.Whether the publishers of BitTorrent metafiles violate copyrights bylinking to copyrighted material without the authorization of copyrightholders is controversial.

Several studies of BitTorrent indicate that a large portion of filesavailable for download via BitTorrent contain malware. In particular,one small sample indicated that 18% of all executable programs availablefor download contained malware. Another study claims that as much as14.5% of BitTorrent downloads contain zero-day malware.

In contrast to potentially untrusted or risky sources such as BitTorrentabove, in other cases, applications may be installed on mobile devicesby users from known good sources. For example, a common source ofapplications installed on mobile devices using the Android system is theGoogle Play store.

The Android system requires that all installed applications be digitallysigned with a certificate whose private key is held by the application'sdeveloper. The Android system uses the certificate as a means ofidentifying the author of an application and establishing trustrelationships between applications. The certificate does not need to besigned by a certificate authority. Rather, it is typical for Androidapplications to use self-signed certificates.

Android applications that are not signed will not be installed on anemulator or a device. When a developer is ready to release anapplication for end-users, the developer signs it with a suitableprivate key. The developer can use self-signed certificates to sign thedeveloper's applications. No certificate authority is needed.

The Android system tests a signer certificate's expiration date only atinstall time. If an application's signer certificate expires after theapplication is installed, the application will continue to functionnormally. The developer can use standard tools (e.g., Keytool andJarsigner) to generate keys and sign the developer's application .apkfiles.

The Android system will not install or run an application that is notsigned appropriately. This applies wherever the Android system is run,whether on an actual device or on the emulator.

When a developer builds in release mode, the developer uses its ownprivate key to sign the application. When the developer compiles theapplication in release mode, a build tools uses the developer's privatekey along with a Jarsigner utility to sign the application's .apk file.Because the certificate and private key used are owned by the developer,the developer provides the password for the keystore and key alias. Someaspects of application signing may affect how the developer approachesthe development of its application, especially if the developer isplanning to release multiple applications.

In general, the recommended strategy for all developers is to sign allof the developer's applications with the same certificate, throughoutthe expected lifespan of these applications. As the developer releasesupdates to its application, the developer must continue to sign theupdates with the same certificate or set of certificates, if thedeveloper wants users to be able to upgrade seamlessly to the newversion. When the system is installing an update to an application, itcompares the certificate(s) in the new version with those in theexisting version. If the certificates match exactly, including both thecertificate data and order, then the system allows the update. If thedeveloper signs the new version without using matching certificates, thedeveloper must also assign a different package name to theapplication—in this case, the user installs the new version as acompletely new application.

When the developer has an application package that is ready to besigned, the developer can sign it using the Jarsigner tool. To sign theapplication, the developer runs Jarsigner, referencing both theapplication's APK and the keystore containing the private key with whichto sign the APK.

Maintaining the security of a private key is of critical importance,both to the developer and to the user. If the developer allows someoneto use the developer's key, or if the developer leaves its keystore andpasswords in an unsecured location such that a third-party could findand use them, the developer's authoring identity and the trust of theuser are compromised.

If a third party should manage to take a developer's key without thedeveloper's knowledge or permission, that person could sign anddistribute applications that maliciously replace the developer'sauthentic applications or corrupt them. Such a person could also signand distribute applications under the developer's identity that attackother applications or the system itself, or corrupt or steal user data.A developer's reputation depends on the developer securing its privatekey properly, at all times, until the key is expired.

SUMMARY OF THE DESCRIPTION

Systems and methods for determining a source of software that is loadedonto or otherwise sourced by a computing device are described herein.Various embodiments described below relate to determining a source ofapplications or other software obtained over a network (e.g.,applications downloaded to a mobile device from an application storesuch as the Google Play store or the Apple App Store), via a connectionto another device (e.g., such as when a wearable, implantable, oringestible device may be provisioned with an application via aconnection to a user's phone or other mobile device), or otherwiseobtained.

In various embodiments, an action may optionally be performed inresponse to the determination of the source of software (e.g., thehandling of an application on the mobile device may be based on whetherthe source of the application is trusted or untrusted; if untrusted,installation of the software can be blocked, or the software can bedisabled or removed from the device). In another example, a softwareapplication being newly-installed on a mobile device of a user may bedetermined to be a fraudulent or tampered version, in which caseinstallation is blocked and an administrator server that manages thedevice via mobile device management (MDM) is notified that the source ofthe application is untrusted. Some embodiments are summarized below.

In one embodiment, a method includes: determining, by a first computingdevice (e.g., a mobile device), whether a first source identifier(source ID) of a first application matches a white list of sourceidentifiers; determining whether the first source identifier matches ablack list of source identifiers; and sending, by the first computingdevice to a second computing device (e.g., a side-load server), at leastone message comprising the first source identifier and a firstapplication identifier for the first application.

In some embodiments, the first computing device stores a device statethat can be set to a value of trusted or untrusted, and the firstcomputing device stores data for a plurality of applications of thefirst computing device. The data includes an application state and asource identifier for each of the applications, and each applicationstate can be set to a value of known or unknown.

In one embodiment, a method includes: storing, by a first computingdevice (e.g., a side-load server), data for a plurality of applicationsassociated with a second computing device (e.g., a mobile device), thedata comprising a state designation for each of the applications,wherein the state designation can be set to values including trusted anduntrusted; receiving, by the first computing device from the secondcomputing device, a first application identifier and a first sourceidentifier, each for a first application; setting, by the firstcomputing device, a first state designation for the first application,wherein the first state designation is to be used for setting a state onthe second computing device; and sending, by the first computing device,the first state designation to the second computing device.

In one embodiment, a system (e.g., a side-load server) includes: atleast one processor; and memory storing instructions configured toinstruct the at least one processor to: receive, from a first computingdevice (e.g., a mobile device), a first application identifier and afirst source identifier, each for a first application of the firstcomputing device; determine whether the first source identifier matchesa white list of source identifiers (e.g., a list of trusted channelidentifiers); and determine whether the first source identifier matchesa black list of source identifiers (e.g., a list of untrusted channelidentifiers); send the first application identifier and the first sourceidentifier over a network to a second computing device (e.g., anadministrator server); receive, from the second computing device, afirst state designation for the first application; set a second statedesignation based on the first state designation; and send the secondstate designation to the first computing device.

In one example, the side-load server stores numerous state designationsfor applications of the mobile device, and the administrator server alsostores numerous state designations for the applications of the mobiledevice. These state designations are not necessarily identical (e.g., astate designation for a given application may be different on eachcomputing device). The state designations are used in variousembodiments for setting an application state and/or a mobile devicestate on the mobile device.

Also, in another example, the side-load server, the administratorserver, and the mobile device may each store black and white lists ofsource identifiers. These lists may be different on each of thesecomputing devices.

In one embodiment, a method includes: receiving, by a first computingdevice from at least one of plurality of computing devices, a firstapplication identifier and a first source identifier, each for a firstapplication; setting, by the first computing device, a first statedesignation for the first application, wherein the first statedesignation is to be used for setting a state on a second computingdevice; and sending, by the first computing device, the first statedesignation to the second computing device.

In one embodiment, a system includes: at least one processor; and memorystoring instructions configured to instruct the at least one processorto: receive, from a first computing device, a first applicationidentifier and a first source identifier, each for a first applicationof the first computing device; determine whether the first sourceidentifier matches at least one of a white list of source identifiers ora black list of source identifiers; send the first applicationidentifier and the first source identifier over a network to a secondcomputing device; receive, from the second computing device, a firststate designation for the first application; set a second statedesignation based on the first state designation; and send the secondstate designation to the first computing device.

In one embodiment, a system includes: at least one processor; and memorystoring instructions configured to instruct the at least one processorto: determine whether a first source identifier of a first applicationmatches at least one of a white list of source identifiers or a blacklist (e.g., in some cases only one type of list, such as only a whitelist, may be used; in other cases, both a white list and black list areused) of source identifiers; and send, to a computing device, the firstsource identifier and a first application identifier for the firstapplication.

The disclosure includes various methods and devices which perform theabove methods and systems, including data processing systems whichperform these methods, and computer readable media containinginstructions which when executed on data processing systems cause thesystems to perform these methods.

Other features will be apparent from the accompanying drawings and fromthe detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which like referencesindicate similar elements.

FIG. 1 shows a system for protection against side-loaded applications,in which user terminals and mobile devices communicate with a side-loadserver, according to various embodiments.

FIG. 2 shows an application marketplace offering multiple applicationsfor remote installation on mobile devices, according to one embodiment.

FIG. 3 shows the system of FIG. 1 further illustrating an administratorserver communicates with the side-load server, according to variousembodiments.

FIG. 4 shows the system of FIG. 3 further illustrating statedesignations are stored at the side-load server and the administratorserver, according to various embodiments.

FIG. 5 shows a system for protection against side-loaded applications,in which a side-load server communicates with an authenticity serverregarding applications installed or being installed on a mobile device,according to one embodiment.

FIG. 6 shows a display of a mobile device of a user, in which thedisplay presents an icon to the user for an application store, accordingto one embodiment.

FIG. 7 shows the display of the mobile device of FIG. 6, on which anotification is presented to the user for approving installation of asoftware client on the mobile device, according to one embodiment.

FIG. 8 shows the display of the mobile device of FIG. 6, on which anotification is provided to query a user whether to trust an applicationfrom a software developer, according to one embodiment.

FIG. 9 shows the display of the mobile device of FIG. 6, on which anotification is provided from a side-load server or an administratorserver indicating that an application being installed may be from anuntrusted source, according to one embodiment.

FIG. 10 shows a user console of a side-load server in communication viaan application programming interface with a user console of anadministrator server, according to one embodiment.

FIG. 11 shows a block diagram of a computing device (e.g., a side-loadserver, an administrator server, or an authenticity server) which can beused in various embodiments.

FIG. 12 shows a block diagram of a computing device (e.g., a mobiledevice of a user or a user terminal), according to one embodiment.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding. However, in certain instances, wellknown or conventional details are not described in order to avoidobscuring the description. References to one or an embodiment in thepresent disclosure are not necessarily references to the sameembodiment; and, such references mean at least one.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

As used herein, “side-loading” or “side-loaded” as used to characterizean application or other software indicates obtaining or obtained from asource that is not the default authorized channel for obtainingapplications for the type of device (e.g., the default channel may beset by the administrator of the device such as by using an administratorserver, or be set by any computing device different than the device ontowhich the application is to be installed). Examples of a source that isnot the default authorized channel include a source that is not trusted,not known, or not authorized.

A source may be trusted for various reasons, including, for example,that the source is an authorized Google Play store or Apple App Store.Other examples include a source identified by an administrator of mobiledevices (e.g., for a large corporation with thousands of employees) foruse by users in downloading new software. In another example, a sourcemay be trusted based on a prior history with that source (e.g.,extensive prior downloads without negative incidents). Also, a source ofprior copies of software may have been previously trusted, but at thetime of sourcing a particular software file or component, the source isuntrusted, so that the software is considered as being side-loaded.

Other examples of a side-loaded application include an applicationobtained from a source that is not known, and thus is untrusted, forexample because there is no prior history of interaction with thesource, or there is no independent confirmation or information that thesource can be trusted. In another example, when referring to Androidapps, an application is side-loaded if it is installed using anapplication package in APK format onto an Android device, afterdownloading the application package from a website other than GooglePlay. This side-loading is possible if the user has allowed “UnknownSources” in her security settings on her computing device (this settingallows the installation of non-market apps).

The embodiments set forth herein are implemented using a wide variety ofdifferent types of computing devices. As used herein, examples of a“computing device” include, but are not limited to, a server, acentralized computing platform, a system of multiple computingprocessors and/or components, a mobile device, a user terminal, avehicle, a personal communications device, a wearable digital device, anelectronic kiosk, a general purpose computer, an electronic documentreader, a tablet, a laptop computer, a smartphone, a digital camera, aresidential domestic appliance, a television, or a digital music player.

As mentioned above, an admin defines and deploys policies for anorganization. In some embodiments, the organization may be a family orother social group, and the administrator role may be performed by aparent or guardian, or may be performed by a third party serviceprovider. Such a third party service provider may be a provider ofsecurity services, or the network operator, or a provider of contentservices. The additional levels of protection and control thatorganizations such as enterprises desire can also be advantageous forconsumers, but consumers are typically not knowledgeable enough toperform administrator roles. Thus, there is often a need for third partyservice providers to act as technically-oriented admins. The consumer orparent or guardian as an admin may specify preferences corresponding tohigh-level policy decisions, and a technical admin can configureunderlying services to meet these high-level policy decisions. As usedin this disclosure, the term “administrator” or “admin” includes, but isnot limited to, all such administrators (e.g., technical admin,consumer, parent, guardian, service provider, etc.) as described in thisparagraph.

As mentioned above, users of mobile devices install applications fromnumerous various sources that are beyond the control of anadministrator. In some embodiments, within a mobile network, the networkoperator can perform various admin functions as described in thisdisclosure. Also, the embodiments described herein are not limited touse solely in enterprise BYOD situations, but are also useful, forexample, in other cases such as where a consumer wishes to administerall devices for the members of her family, or all of her personaldevices (e.g., phone, watch, laptop, desktop computer, etc.).

As used herein, a “component” means a part of an application (e.g., anapplication that is installed by a user from an Android or othersoftware application marketplace and then executes on a mobile device).In one example, a component is provided by the application's creator orby a third party. In another example, the component may be code providedby an ad network or an analytics network.

In yet another example, components are linked libraries/SDKs that arepackaged within an application. This is code that is within theapplication, but the code is developed by a third party and provides theability for an application developer to integrate certain behaviors ofthat component into the developer's application (e.g., displaying acertain type of ads from a certain ad network such as LeadBolt). Inanother example, a set of data (e.g., in a file or a database) that isused by an application may be considered as a component of thatapplication. Also, in some examples, data used by an application can beconsidered as known or unknown, or trusted or untrusted.

In one embodiment, a component (e.g., a component associated with an adnetwork) may have multiple behaviors associated with it (e.g.,notification display, settings changes, and/or information collection).For example, the behaviors of the BTController application (discussedfurther below) is the summation of the behaviors of its constituentcomponents. In some cases, components may provide the ability toselectively opt-out of individual behaviors. However, in other cases,this is not possible, and in order to opt out of any set of behaviors, auser must opt-out of the entire component.

Various embodiments described below for side-load protection relate todetermining a source of software that is loaded on or otherwisetransferred to a computing device. It is typically desired to determinethe source in order to assess the risk of the software and make adetermination or decision whether further action should be taken withrespect to the software such as, for example, blocking installation ofthe software onto the computing device.

Sources of software (e.g., software loaded by user onto her laptopcomputer or mobile device) may include various numerous, non-limitingexamples. For example, sources may include various channels ofdistribution for software applications. These channels may include theGoogle play store or the Apple App Store, other websites, various filesharing or transfer servers, peer-to-peer file-sharing systems (e.g.,BitTorrent), and other network or computer system transfer sources forsoftware. In addition to the foregoing types of sources, other sourcesinclude software accessed are installed locally such as by userinserting a USB memory drive into a computing device, or pairing twomobile devices using a Bluetooth connection.

There are various ways that a source of an application can bedetermined. In one embodiment, the source of an app on Android can bedetermined by calling getInstallerPackageName( ) In another embodiment,a source of software may be, for example, the “default” and/or “normal”channel for an operating system (OS) or other software, such as definedby an administrator server that manages computing devices for anenterprise.

In various embodiments, channels can be considered or deemed to bewhite-listed or black-listed. White-listed channels are trusted, andblack-listed channels are untrusted. For example, applications fromwhite-listed channels are generally considered as being trustedsoftware, and applications from black-listed channels are generallyconsidered as being untrusted software.

The software itself that is side-loaded includes various examples. Forexample, the software may be an application, a widget, an executablefile, binary code, firmware, operating system components or updates, andother forms of executable software. Examples further include otherfiles, such as office documents or PDF files, that may containcomponents like scripts or macros which are themselves executable. Insome cases, such an embedded executable component may have associatedwith it identifiers or signing key information which can be used toseparately determine the source of that executable component. Anapplication itself may contain another application, for example, wherean application for a mobile device which contains within it anotherrelated application which is intended for installation on a wearable orother personal or external device.

In various embodiments, the source of side-loaded software may bedetermined in various ways. For example, channel identifiers (channelIDs) associated with an application may be compared to various whitelists and black lists. In another example, prior experience with thesame or similar software on other computing devices may be used to makean assessment of the source of software being currently installed on aparticular device. For example, various components of acurrently-sourced software application can be identified and compared tocomponents of software previously analyzed for prior installations madeon other computing devices.

In another example, characteristics (e.g., a signing certificate orother signature of an application) associated with the developer of thesoftware may be used to determine the source. In another example, thebehavior of software either as installed on a mobile device or asdetermined by execution in a controlled environment may be used formaking an identification of the source of the software. For example, thebehavior of software newly being installed may be the same or similar asprior known malware.

In various embodiments, as each software application is assessed formaking a determination of source, a source identifier is associated withthe software. The source identifier is used by a mobile device or othercomputing device on which the software is being installed. The mobiledevice can communicate with a side-load server using the sourceidentifier as a basis for side-load protection activities, as discussedbelow. An application identifier is also associated with the softwarefor tracking data related to the application. In one embodiment, anapplication identifier is an identifier used to identify a particularapplication. Examples of such identifiers include an application packagename, an application title and version, or an arbitrary identificationnumber (binary or otherwise).

In some embodiments, even a trusted source (e.g., the Google Play Store)may provide certain applications that are unauthorized or undesirable inat least one aspect. For example, a banking enterprise may authorizeobtaining of a banking application from a designated enterprise website(e.g., a Bank of America website to which a user or a mobile deviceauthenticates itself). An administrator of the enterprise desires thatusers download the banking application from this designated website,which the administrator considers to be a trusted source. However, auser might download the same or similar banking application from anothersource. This other source may be trusted for most applications. Forexample, the Google Play Store may be considered by an administratorserver to be a trusted source for most applications downloaded to adevice.

However, for the above particular banking application, the enterpriseadministrator only considers the application to be obtained from atrusted source if that source is the designated website. Any bankingapplication obtained from the Google Play Store is considered to havebeen obtained from an untrusted source.

A source (such as previously identified and assigned to a sourceidentifier) from which an undesirable application has been obtained canbe set to or marked as being untrusted (either generally for allsoftware obtained from that source, or untrusted, but only with respectto certain defined software). For the example of the banking applicationabove, the Google Play Store can be deemed to be untrusted source forthis application.

In one embodiment, side-load server 150 stores data that associatessource identifiers with application identifiers of those applicationsfor which the respective source is considered untrusted (e.g., thebanking application from the Google Play Store above). This stored datais used in later comparisons of source identifiers for new applicationsbeing installed on a computing device. The source identifier for a newapplication is compared to such previously-associated sourceidentifier/application identifier records. If the new application isdetermined to be the same as or similar to the previous application(e.g., a previous application obtained in an unauthorized manner fromthe Google Play Store), than the new application is likewise consideredto have been obtained from an untrusted source. For example, thesimilarity of the new application to the previous application can bedetermined by component analysis as described herein. In one case, anew, same-or-similar banking application obtained from the Google PlayStore has an application state (or a state designation) set to untrustedin response to this determination.

In various embodiments, a mobile device on which an application is beinginstalled stores state data. The state data includes a mobile devicestate and an application state for each application stored on orinstalled on the mobile device. The mobile device state may have valuesincluding trusted, untrusted, and unknown. The state of unknownindicates that a determination has not yet been made whether the mobiledevice is trusted or untrusted, or that an event has occurred on thedevice which could require re-assessment and could change the mobiledevice state. The application state may have values including trustedand untrusted. An application having a state of untrusted will, forexample, not be executed.

Various embodiments described below also discuss state designations. Astate designation is generally an indication by a computing device to beused by another computing device for setting a state. The statedesignation may have values of trusted and untrusted. The state may bethe mobile device state or an application state. For example, the mobiledevice may receive a state designation from a side-load server and thenset the mobile device state (or alternatively an application state)based on the state designation. An application identifier will beassociated with the state designation in order to identify theapplicable application.

In some cases, the side-load server communicates with an administratorserver, which itself may make determinations of state designations thatare sent to the side-load server. The side-load server uses a statedesignation from the administrator server in order to make a decision atthe side-load server regarding a state designation to send to the mobiledevice. The state designations may be selected based on various factorsincluding the source of software, its source identifier, component orbehavior analysis of software, etc., as discussed herein.

In various embodiments, based on the mobile device state and/or theapplication state, various actions may be performed with respect to themobile device. For example, the mobile device may be denied access to acorporate network, or an application may be disabled.

In some embodiments, the source of the application may be determinedduring the process of assessing authenticity of the application, asdiscussed herein. For example, an application that is determined as notbeing authentic can have its source added to a blacklist.

In some embodiments, an application can be monitored for fraudulentbehavior. If fraudulent behavior is identified, the source of theapplication can be added to a blacklist.

In some embodiments, installation of an application onto a computerdevice can be monitored. The signature associated with the applicationor other characteristics of the signer of the application can be used toassess the source.

In some embodiments, the manner of usage of an application on acomputing device can be monitored. The usage or behavior of componentsof the application on the device that are inconsistent with a user oradministrator-designated policy can be identified. In such event, thesource and/or the application can be deemed as untrusted.

There are various examples of policies that may be used on mobile orother computing devices. For example, a user policy may define thehandling of components 104 and 106 on mobile device 149. A policy may bedefined by behavioral preferences established by a user and/or anadministrator, and this policy is enforced on new applications installedon the mobile device. In another example, a policy may apply to aparticular identified application.

In other examples, policies may be defined and applied to control orrestrict the behavior of applications and their components. This caninclude the identification of advertising networks and defining policiesto permit various opt-out actions for these advertising networks.

In some embodiments, a component analysis of an application can be usedto relate components of a new application to a database ofcharacteristics for known bad components. If the component in the newapplication corresponds to a known bad component, the source of thesoftware can be identified as untrusted.

In various embodiments, side-load protection services are used by anadministrator of numerous mobile devices, for example, for a companyhaving thousands of employees. Mobile device management software isexecuted on an administrator server that provides a console for theadministrator. The console provides information to the administratorregarding source information and statistics for side-loaded applicationsof managed devices. The administrator server communicates with theside-load server as part of the side-load protection services.

Side-Load Protection

FIG. 1 shows a system for protection against side-loaded applications,in which user terminals 141-145 and mobile devices 147-149 communicatewith a side-load server 150, according to various embodiments. Mobiledevices may include, for example cell phones, smartphones, and tabletdevices such as the iPhone device or an Android tablet. Mobile devicesmay also include automobiles, planes, or other vehicles that include acomputing device, such as an embedded computing or communication systemthat communicates via the Internet over a cellular phone system, orother portable computing devices (e.g., devices that pair with a mobiledevice using Bluetooth, such as an Apple watch). The mobile devicescommunicate with side-load server 150 and optionally an applicationmarketplace 123, and/or a developer server 160, according to variousembodiments as described below.

Additional examples of mobile devices include devices that are part ofwhat is called “the Internet of things” (IOT). In the internet of thingsthere are multiple devices which operate on their own, withoutaccompanying and attendant users. Such devices may be mobile or sessile;they may have various sensors and computing and communicationcapabilities and may run applications; schematically they can beconsidered substantially similar to a mobile device. Such “things” mayhave occasional interactions with their owners or administrators, whomay monitor the things or modify settings on these things. Such ownersor administrators play the role of users with respect to the “thing”devices. In some examples, the primary mobile device of a user may be anadministrator server with respect to a paired “thing” device that isworn by the user (e.g., an Apple watch). In an embodiment, a “thing” ora device, e.g., one intended for use as a health or medical device, mayhave an embedded white list defining trusted sources for applications,or may have an administrator associated with that device, e.g., anadministrator working for the medical device manufacturer ordistributor, who can control the side-loading policies for that device.

More specifically, in FIG. 1, the user terminals (e.g., 141, 143, . . ., 145) and/or mobile devices (e.g., 147, 149) are used to access and/orcommunicate with side-load server 150, application marketplace 123(e.g., an Android or Google Play store or marketplace, or an enterpriseapplication store), and/or developer server 160 over a communicationnetwork 121 (e.g., the Internet, a wide area network, a local network,or other wired or wireless communications network).

Network 121 may be used to download and remotely install applicationsselected from marketplace 123 (e.g., using Google Play or the AndroidMarket). Marketplace 123 may include one or more web servers (or othertypes of data communication servers) to communicate with the userterminals (e.g., 141, 143, . . . , 145) and mobile devices 147, 149.

Specifically, mobile device 149 may download a new application 1013 fromapplication marketplace 123 or developer server 160. An applicationobtained from developer server 160 is signed using a signing certificate162. New application 1013 has components 104 and 106.

In an alternative embodiment, an application or other software has beenpreloaded onto mobile device 149. In this case, assessment of thisapplication alone (or assessment of this application along with a set ofor all applications installed on mobile device 149) can be performed. Inone embodiment, this preloaded application includes components that areassessed and handled such as described herein for new applications beinginstalled on a mobile or other computing device.

Mobile device 149 stores a user policy 108. The new application 1013 maybe compared to user policy 108 during or after installation. Side-loadedserver 150 includes a data repository of user policies 116. User policy108 of mobile device 149 may be compared to user policies 116. Anadministrator server (not shown) may provide some policies in userpolicies 116 (e.g., as regards usage of or installation of applicationsonto mobile device 149).

In one example, an owner of an Android phone (e.g., mobile device 149)may visit a web site hosted by marketplace 123 and select a free pokergame application for remote installation on mobile device 149. The usermay authenticate itself to marketplace 123 by its email address (e.g.,Gmail address) and password.

The marketplace 123 is connected to respective data storage facilitiesto store applications, messaging account data for users, user preferencedata, and other data. A messaging server (not shown) may be connected tocommunication network 121 to deliver messages (e.g., email or text) touser terminals 141-145 or one of a user's mobile devices 147, 149.

In one embodiment, a software server (not shown) may be coupled tocommunicate with application marketplace 123 and/or mobile devices 147,149 by communication network 121. The software server stores, forexample, an application (e.g., the Ad Network Detector discussed below)in memory. The application stored on the software server is sent toapplication marketplace 123, where it is stored for later download andinstallation by a user. For example, the user of mobile device 149 mayaccess marketplace 123 to download and install the application. Inanother embodiment, the software server is developer server 160, oranother computing device, and may be used to upload an application tomarketplace 123.

In one embodiment, the software server communicates with the application(now executing on mobile device 149 after installation by the user). Theapplication is configured to identify at least one behavior on mobiledevice 149 as discussed herein. The at least one behavior is associatedwith each of a plurality of components of a plurality of otherapplications installed on the mobile device 149 (e.g., otherapplications previously downloaded by the user from the Google Playservice), and the at least one behavior includes a first behaviorassociated with a first component.

Side-load server 150 may receive at least one behavioral preference ofthe user (e.g., from mobile device 149 and/or from an administrator ofthe mobile device). The at least one behavioral preference may bedetermined by the application based on input from the user (e.g., a userselection from a menu or results list) or the administrator.

The side-load server stores the at least one behavioral preference(e.g., stores in a memory of the server) for later uses such asresponding to queries from other computing devices regarding the intentof the user of mobile device 149. In one embodiment, the Ad NetworkDetector discussed below may manage these behavioral preferences onbehalf of a user for these networks.

Although not illustrated in the figures, an identity server may becoupled to communication network 121. The identity server maycommunicate with, for example, side-load server 150. For example,side-load server 150 may obtain information from the identity serverregarding one or more software components for a side-loaded applicationbeing analyzed to determine its source.

In an alternative embodiment, the identity server includes a database,which stores component identities (and optionally some or all of userpolicies 116). Mobile device 149 may include applications that have beenpreviously installed on mobile device 149. These applications may beinstalled from application marketplace 123 or developer server 160.

The user policy 108 is stored locally in a memory of mobile device 149.In one embodiment, during operation, as discussed in more detail below,user policy 108 may be used to define the handling of components 104 and106 on mobile device 149.

In one embodiment, a user policy for mobile device 149 may alternatively(or in addition to user policy 108) be stored as one of user policies116 on the side-load server 150 and/or the identity server. A user oradministrator policy may be enforced on mobile device 149 using either alocal user policy or a remote user policy, or a combination thereof.

As discussed in more detail below, after an application 102 is installedon mobile device 149, components 104 and 106 may be identified andbehaviors exhibited on mobile device 149 may be attributed to one ormore of components 104 and 106. Any given component (e.g., component104) may be present in several different applications on mobile device149 and/or may be common to numerous copies or versions of anapplication that have been installed on mobile or other computingdevices for large numbers of other users. In one embodiment, thiscommonality of component presence permits observing and collectingstructural and behavioral data associated with the component (e.g., howthe component behaves on other mobile devices). This known componentdata may be stored in a database (not shown) of side-load server 150,and the component data may be associated with a particular componentidentity. Thus, a data repository of prior component data can be used tocompare to data more recently obtained for new components (such as thoseidentified in newly-installed applications on mobile device 149). Theresults of the component comparison can also be used when determining asource of an application.

More specifically, as characteristics and behaviors associated withcomponents on mobile device 149 are identified and attributed, thesecharacteristics and behaviors may be compared with known characteristicsand behaviors stored either locally on mobile device 149 or storedremotely on the identity server (which was discussed above) as dataassociated with component identities (these identities may also beassociated with previously-determined sources of the correspondingapplications). The results from such comparisons in combination withdetermination of source, and/or mobile device state or applicationstate, may be used for making decisions regarding configuration and/ordisabling of one or more particular components on the mobile device orother computing device (e.g. user terminal 141), as discussed in greaterdetail below.

Although FIG. 1 illustrates an exemplary system implemented inclient-server architecture, embodiments of the disclosure can beimplemented in various alternative architectures. For example, theside-load server 150 may be implemented via a peer to peer network ofuser terminals in some embodiments, where applications anddata/information from mobile devices are shared via peer to peercommunication connections.

In some embodiments, a combination of client server architecture andpeer to peer architecture can be used, in which one or more centralizedservers may be used to provide some of the information and/or servicesand the peer to peer network is used to provide other information and/orservices. Thus, embodiments of the disclosure are not limited to aparticular architecture.

FIG. 2 shows a web page of an application marketplace 123 (e.g., theGoogle Play service) offering multiple applications (A, B, C) for remoteinstallation on mobile devices, according to one embodiment. A useraccesses the web page and selects an application for remoteinstallation. The user may pay for the application on a web pageprovided by marketplace 123 (unless the application is free of charge).The application marketplace 123 may be a trusted source of applications.It should be noted that in other embodiments, a marketplace such asGoogle Play is not limited to access only via a web page, but also maybe accessed via an application installed on a mobile device, such as theGoogle “Play Store” application on Android.

An example of an application available for download from the Google PlayStore is an application known as “BTController”. Some user reviews forthis application have included complaints about excessive advertisementson the user's mobile device after installation. Thus, this may beconsidered an undesirable application (e.g., Google Play could bedefined as untrusted with respect to this particular application). Forexample, side-load server 150 can store a record associating a sourceidentifier for the Google Play Store with an application identifier forthis undesirable application. In response to a request from a mobiledevice requesting a state designation for a new application beinginstalled on the mobile device that has been determined to be similar tothis undesirable application, side-load server 150 sends a statedesignation having a value of untrusted.

FIG. 3 shows the system of FIG. 1 further illustrating an administratorserver 302 communicating with the side-load server 150, according tovarious embodiments. Administrator server 302 stores user policies 308,which relate to mobile device management of mobile device 149 and othermobile devices. User policies 308 may be shared with side-load server150, as mentioned above. In an alternative embodiment, side-load server150 and administrator server 302 could be the same computing device.

Administrator server 302 and side-load server 150 communicate duringside-load protection using network 121. This communication includessharing of data regarding applications associated with mobile device149, and the providing of state designations from administrator server302 to side-load server 150. The provided state designations may bebased on data repositories and analysis of an application and/or itssource as performed by administrator server 302.

Mobile device 149 stores state data 306 and mobile application data 304.State data 306 includes a mobile device state and an application statefor each of the applications installed or stored on mobile device 149.The mobile device state and the application state may be set based oncommunications received from side-load server 150.

The mobile application data 304 includes an application identifier foreach application of mobile device 149 and a source identifier for eachsuch application. This source identifier identifies the source fromwhich the application has been obtained. In one example, this source isa channel identifier provided in a field of data for an applicationpackage downloaded from an application marketplace. In other cases, theapplication does not contain any identification of source, but a sourceis determined and assigned to the application based on analysis of theapplication, or by observation of how an application file is provisionedto a computing device, as described herein.

FIG. 4 shows the system of FIG. 3 further illustrating statedesignations stored at the side-load server 150 and the administratorserver 302, according to various embodiments. More specifically,side-load server 150 stores server application data 402 and furthercomprises a source database 406. Application data 402 includes a set ofrecords, each record for an application stored on mobile device 149, andthe record including an application identifier, a corresponding sourceidentifier, and a state designation.

The application identifier and source identifier are received frommobile device 149, for example, in one or more messages. In reply tothese messages, side-load server 150 sends a message with one or morestate designations for each application identifier. Side-load server 150compares source identifiers from mobile device 149 with sourceidentifiers in white list 408 and black list 410 of source database 406.White list 408 contains a list of source identifiers that have beenpreviously determined to be trusted. Black list 410 includes a list ofsource identifiers that have been previously determined to be untrusted.

In some cases, side-load server 150 determines and sends statedesignations to mobile device 149 without any interaction withadministrator server 302. However, in other cases, side-load server 150sends a message to administrator server 302 providing an applicationidentifier and source identifier along with the requests thatadministrator server 302 determine a state designation.

Administrator server 302 stores administrator application data 404,which includes application identifiers and source identifiers receivedfrom side-load server 150. Administrator server 302 determines anadministrator state designation for an application, as was mentionedabove. This administrator state designation is sent to side-load server150, which uses the administrator state designation to set a statedesignation of the side-load server for sending to mobile device 149.The state designation sent to mobile device 149 may be different thanthe administrator state designation that was received by side-loadserver 150.

Various non-limiting embodiments for side-load source assessment andprotection are now described below. In one embodiment, a non-transitorycomputer-readable storage medium stores computer-readable instructions,which when executed, cause a first computing device to: determine, bythe first computing device, whether a first source identifier of a firstapplication matches a white list of source identifiers; determinewhether the first source identifier matches a black list of sourceidentifiers; and send, by the first computing device to a secondcomputing device, at least one message comprising the first sourceidentifier and a first application identifier for the first application.

In one embodiment, the determining whether the first source identifiermatches the black list is performed in response to the first sourceidentifier not matching the white list. In one embodiment, thedetermining whether the first source identifier matches the white listis performed in response to the first source identifier not matching theblack list. In one embodiment, the determining whether the first sourceidentifier matches the white list is performed simultaneously with thedetermining whether the first source identifier matches the black list.

In one embodiment, the computer-readable instructions further cause thefirst computing device to, in response to the first source identifiermatching the black list, set a device state of the first computingdevice to untrusted, and send the at least one message to the secondcomputing device, the at least one message further comprising the devicestate. The computer-readable instructions may further cause the firstcomputing device to store the device state, wherein the device state canbe set to values including trusted and untrusted.

In one embodiment, the computer-readable instructions further cause thefirst computing device to, in response to the first source identifiernot matching the black list, set a first application state for the firstapplication to unknown, and send the at least one message to the secondcomputing device, the at least one message further comprising the firstapplication state. The computer-readable instructions may further causethe first computing device to store data for a plurality ofapplications, the data comprising an application state and a sourceidentifier for each of the applications, wherein each application statecan be set to values including known and unknown.

In one embodiment, the computer-readable instructions further cause thefirst computing device to receive a message from the second computingdevice, the message comprising a first state designation for the firstapplication. In one embodiment, the computer-readable instructionsfurther cause the first computing device to set the device state to thefirst state designation. In one embodiment, the device state is set tothe first state designation only if a device state of the firstcomputing device is not set to untrusted.

In one embodiment, the computer-readable instructions further cause thefirst computing device to, prior to determining whether the first sourceidentifier matches the white list, receive the white list from thesecond computing device. In one embodiment, the first computing deviceis a vehicle, a personal communications device, a wearable digitaldevice, an electronic kiosk, a general purpose computer, an electronicdocument reader, a tablet, a laptop computer, a smartphone, a digitalcamera, a residential domestic appliance, a television, a digital musicplayer, or a computing device that is embedded in a vehicle or otherpiece of machinery.

In one embodiment, a method includes: storing, by a first computingdevice, data for a plurality of applications associated with a secondcomputing device, the data comprising a state designation for each ofthe applications, wherein the state designation can be set to valuesincluding trusted and untrusted; receiving, by the first computingdevice from the second computing device, a first application identifierand a first source identifier, each for a first application; setting, bythe first computing device, a first state designation for the firstapplication, wherein the first state designation is to be used forsetting a state on the second computing device; and sending, by thefirst computing device, the first state designation to the secondcomputing device. The state to be set may be a device state, or anapplication state for an application stored on the second computingdevice.

In one embodiment, the setting the first state designation comprises:sending, by the first computing device, over a network, the firstapplication identifier and the first source identifier to a thirdcomputing device; receiving, from the third computing device, a secondstate designation for the first application; and setting the first statedesignation based on the second state designation.

In one embodiment, the setting the first state designation comprises:determining whether the first source identifier matches a white list ofsource identifiers; and in response to the first source identifiermatching the white list, setting the first state designation to trusted.

In one embodiment, the setting the first state designation comprises:determining whether the first source identifier matches a white list ofsource identifiers; and in response to the first source identifier notmatching the white list, determining whether the first source identifiermatches a black list of source identifiers.

In one embodiment, the setting the first state designation furthercomprises, in response to the first source identifier matching the blacklist, setting the first state designation to untrusted. In oneembodiment, the setting the first state designation further comprises,in response to the first source identifier not matching the black list:sending the first application identifier and the first source identifierto a third computing device; and setting the first state designationbased on a second state designation received from the third computingdevice. In one embodiment, the method further comprises updating theblack list based on the second state designation.

In one embodiment, a system includes: at least one processor; and memorystoring instructions configured to instruct the at least one processorto: receive, from a first computing device, a first applicationidentifier and a first source identifier, each for a first applicationof the first computing device; determine whether the first sourceidentifier matches a white list of source identifiers; and determinewhether the first source identifier matches a black list of sourceidentifiers; send the first application identifier and the first sourceidentifier over a network to a second computing device; receive, fromthe second computing device, a first state designation for the firstapplication; set a second state designation based on the first statedesignation; and send the second state designation to the firstcomputing device.

In one embodiment, the determining whether the first source identifiermatches the black list is performed in response to the first sourceidentifier not matching the white list. In one embodiment, the sendingthe first application identifier and the first source identifier to thesecond computing device is performed in response to the first sourceidentifier not matching the black list. In one embodiment, theinstructions are further configured to instruct the at least oneprocessor to update the white list based on the first state designation.

In one embodiment, the system further comprises a database storing datafor a plurality of applications associated with the first computingdevice, the data comprising a source identifier and a state designationfor each of the applications, wherein each state designation can be setto values including trusted and untrusted.

In one embodiment, the first source identifier is based on a signatureof the first application. In one embodiment, the instructions arefurther configured to instruct the at least one processor to receive atrusted source identifier from the second computing device, and updatethe white list based on the trusted source identifier. In oneembodiment, the instructions are further configured to instruct the atleast one processor to receive a trusted source identifier from thesecond computing device, and update the black list based on the trustedsource identifier.

FIG. 5 shows a system for evaluating a source for side-loadedapplications, in which a side-load server 150 communicates with anauthenticity server 1005 regarding applications installed or beinginstalled on mobile device 149, according to one embodiment. In making adetermination of the source of side-loaded software for mobile device149, side-load server 150 communicates with mobile device 149 andauthenticity server 1005, and optionally an administrator server (notshown) as discussed above.

Authenticity server 1005 includes a database 1007, which storescomponent data 1009 and a repository 1003. Repository 1003 containspackage identifiers and signing identifiers for applications beinginstalled on mobile device 149. Various embodiments relating toauthenticity server 1005 are discussed in greater detail below.

FIG. 6 shows a display 602 of a mobile device 606 of a user, in whichthe display 602 presents an icon 604 to the user for an applicationstore (e.g., Apple App Store), according to one embodiment. In oneembodiment, mobile device 606 is mobile device 149 of FIG. 1. Display602 presents other icons correspond to applications loaded onto mobiledevice 606.

FIG. 7 shows the display of the mobile device 606, on which anotification 702 is presented to the user for approving installation ofa software client (i.e., “Email Client”) on mobile device 606, accordingto one embodiment. Enterprise administrators typically are not concernedwith malware in an established application store such as the Apple AppStore. Enterprise users are typically trained to install applicationsfrom other sources such as mobile device management and websitesdesignated by the administrator.

FIG. 8 shows the display of the mobile device 606, on which anotification 802 is provided to query a user whether to trust anapplication from an identified software developer, according to oneembodiment. Enterprise signing certificates can be used to sign anapplication so that it can be distributed to any device. Anadministrator of the enterprise may desire that its users only installapplications from an established application marketplace or applicationsthat are signed by the enterprise signing certificate.

FIG. 9 shows the display of the mobile device 606, on which anotification 902 is provided from side-load server 150 or administratorserver 302 indicating that an application being installed may be from anuntrusted source, according to one embodiment. The source of thisapplication has been determined to be an untrusted source based on thevarious methods as described herein.

FIG. 10 shows a user console 1032 of side-load server 150 incommunication via an application programming interface with a userconsole 1034 of administrator server 302, according to one embodiment.Console 1032 provides a display to the user of a variety of informationincluding a list of side-loaded applications detected as potentialmalware, along with metadata for such applications including signers,permissions, and frameworks. The same information may be provided toconsole 1034 over network 121. After detection of malware or otherundesired side-loaded applications, an administrator can controlremediation activities on mobile devices such as mobile device 149.

FIG. 11 shows a block diagram of a computing device 201 (e.g., side-loadserver 150, administrator server 302, or authenticity server 1005),which can be used in various embodiments. While FIG. 11 illustratesvarious components, it is not intended to represent any particulararchitecture or manner of interconnecting the components. Other systemsthat have fewer or more components may also be used. In an embodiment, aside-load server, an administrator server, an authenticity server, or anidentity server may each reside on separate computing systems, or one ormore may run on the same computing device, in various combinations.

In FIG. 11, computing device 201 includes an inter-connect 202 (e.g.,bus and system core logic), which interconnects a microprocessor(s) 203and memory 208. The microprocessor 203 is coupled to cache memory 204 inthe example of FIG. 11.

The inter-connect 202 interconnects the microprocessor(s) 203 and thememory 208 together and also interconnects them to a display controllerand display device 207 and to peripheral devices such as input/output(I/O) devices 205 through an input/output controller(s) 206. Typical I/Odevices include mice, keyboards, modems, network interfaces, printers,scanners, video cameras and other devices which are well known in theart.

The inter-connect 202 may include one or more buses connected to oneanother through various bridges, controllers and/or adapters. In oneembodiment the I/O controller 206 includes a USB (Universal Serial Bus)adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapterfor controlling IEEE-1394 peripherals.

The memory 208 may include ROM (Read Only Memory), and volatile RAM(Random Access Memory) and non-volatile memory, such as hard drive,flash memory, etc.

Volatile RAM is typically implemented as dynamic RAM (DRAM) whichrequires power continually in order to refresh or maintain the data inthe memory. Non-volatile memory is typically a magnetic hard drive, amagnetic optical drive, or an optical drive (e.g., a DVD RAM), or othertype of memory system which maintains data even after power is removedfrom the system. The non-volatile memory may also be a random accessmemory.

The non-volatile memory can be a local device coupled directly to therest of the components in the computing device. A non-volatile memorythat is remote from the computing device, such as a network storagedevice coupled to the computing device through a network interface suchas a modem or Ethernet interface, can also be used.

In one embodiment, a computing device as illustrated in FIG. 11 is usedto implement side-load server 150, application marketplace 123,developer server 160, administrator server 302, and/or other servers.

In another embodiment, a computing device as illustrated in FIG. 11 isused to implement a user terminal or a mobile device on which anapplication is installed or being installed. A user terminal may be inthe form, for example, of a notebook computer or a personal desktopcomputer.

In some embodiments, one or more servers can be replaced with theservice of a peer to peer network of a plurality of data processingsystems, or a network of distributed computing systems. The peer to peernetwork, or a distributed computing system, can be collectively viewedas a computing device.

Embodiments of the disclosure can be implemented via themicroprocessor(s) 203 and/or the memory 208. For example, thefunctionalities described can be partially implemented via hardwarelogic in the microprocessor(s) 203 and partially using the instructionsstored in the memory 208. Some embodiments are implemented using themicroprocessor(s) 203 without additional instructions stored in thememory 208. Some embodiments are implemented using the instructionsstored in the memory 208 for execution by one or more general purposemicroprocessor(s) 203. Thus, the disclosure is not limited to a specificconfiguration of hardware and/or software.

FIG. 12 shows a block diagram of a computing device (e.g., a mobiledevice of a user or a user terminal), according to one embodiment. InFIG. 12, the computing device includes an inter-connect 221 connectingthe presentation device 229, user input device 231, a processor 233, amemory 227, a position identification unit 225 and a communicationdevice 223.

In FIG. 12, the position identification unit 225 is used to identify ageographic location. The position identification unit 225 may include asatellite positioning system receiver, such as a Global PositioningSystem (GPS) receiver, to automatically identify the current position ofthe computing device.

In FIG. 12, the communication device 223 is configured to communicatewith a server to provide data, including application data (e.g., anapplication identifier and a source identifier for a newly-sourcedapplication). In one embodiment, the user input device 231 is configuredto receive or generate user data or content. The user input device 231may include a text input device, a still image camera, a video camera,and/or a sound recorder, etc.

Side-Load Protection Variations

Various non-limiting embodiments and examples related to side-loadprotection and/or determination of a source of side-loaded software arenow discussed below. The embodiments and examples of this section (i.e.,“Side-Load Protection Variations”) do not limit the generality of theforegoing discussion.

In a first embodiment, an application has been installed (or in othercases will be or is planned to be installed) on a mobile device (e.g.,mobile device 149) and a determination is made whether the source of theapplication is from an untrusted channel. For example, for anapplication on an Android mobile device, the application has beenobtained from a source other than the Google Play Store.

Various use cases 1.1-1.6 are described below (pseudocode is used inportions of the discussion below for ease of explanation). These usecases relate to various situations in which one or more applications(sometimes referred to simply as an “app”) are to be installed on, arealready installed on or otherwise interact with, or are intended for useon or with a mobile device. These applications may be tested in variousways as described below. In particular, use cases 1.5-1.6 relate toallowing or disallowing a side-loaded application. In some cases, thisallowing or disallowing may relate to permitting or preventinginstallation of the application, or execution of an application that hasalready been installed. The “Server” and/or “server” mentioned in theuse cases below can be, for example, side-load server 150.

Various acronyms and terms used in the use cases below have thefollowing meanings, with possible values indicated for some terms:

-   MCD-State: Mobile Device State [Trusted/Untrusted/Unknown]-   SD-MCD: State Designation for the Mobile Device [Trusted/Untrusted]-   Admin-MCD-State-Desig: Administrator Mobile Device State Designation    [Trusted/Untrusted]-   App-State: State of the Application [Trusted/Untrusted]-   SD-App: State Designation for the Application [Trusted/Untrusted]-   App-Sig: Signature of Authorship of the Application

Use case 1.1: Testing a single downloaded app (white-listed channels andblack-listed channels)

At the mobile device:

-   -   Download the app,    -   Test the channel ID associated with the app against a first        known list of good channel IDs    -   If a match is not found        -   test the channel ID with a first known list of bad channel            IDs        -   if a match is found            -   set the Mobile Device State (MCD-State) to ‘untrusted’            -   send a message containing the MCD-State, the app id and                the channel to a server        -   else if a match is not found            -   set the MCD-State to ‘unknown’            -   send a message containing the MCD-State, the app id and                the channel to a server            -   receive a message from the server, the message                containing a State Designation for the Mobile Device                (SD-MCD)            -   set the MCD-State based on the received SD-MCD

At the Server:

-   -   Receive message from the mobile device    -   If the MCD-State is ‘unknown’        -   test the channel ID associated with the app against a second            known list of good channel IDs        -   if a match is not found            -   test the channel ID with a second known list of bad                channel IDs            -   if a match is found                -   set the SD-MCD to ‘untrusted’            -   else if a match is not found                -   present a message to an administrator (e.g., admin                    server 302), the message containing the app id and                    the channel ID                -   receive an administrator mobile device state                    designation (Admin-MCD-State-Desig) from the                    administrator                -   set the SD-MCD on the received Admin-MCD-State-Desig                -   update the second known list of good channel IDs or                    the second known list of bad channel IDs based on                    the Admin-MCD-State-Desig            -   send a message to the mobile device containing the                SD-MCD.

Use case 1.2: Testing all apps on the mobile device (white-listedchannels and black-listed channels)

At the mobile device:

-   -   Receive a first known list of good channel IDs    -   Receive a first known list of bad channel IDs    -   For each app to be tested        -   test the channel ID associated with the app against a first            known list of good channel IDs        -   if a match is not found            -   test the channel ID with a first known list of bad                channel IDs            -   if a match is found                -   set the MCD-State to ‘untrusted’                -   send a message containing the MCD-State, the app id                    and the channel to a server            -   else if a match is not found                -   set the state of app (App-State) on the mobile                    device to ‘unknown’                -   send a message containing the App-State, the app id                    and the channel to a server                -   receive a message from the server, the message                    containing a State Designation for the App (SD-App)                    on the mobile device                -   if the MCD-State is not ‘untrusted’                -    set the MCD-State on the received SD-App

At the Server:

-   -   Receive message from the mobile device    -   If the App-State on the mobile device is ‘unknown’        -   test the channel ID associated with the app against a second            known list of good channel IDs        -   if a match is found            -   set the SD-App on the server to ‘trusted’        -   if a match is not found            -   test the channel ID with a second known list of bad                channel IDs            -   if a match is found                -   set the SD-App on the server to ‘untrusted’            -   else if a match is not found                -   present a message to an administrator containing the                    app id and the channel ID                -   receive an administrator mobile device app state                    designation from the administrator                -   set the SD-App on the server based on the received                    administrator mobile device app state designation                -   update the second known list of good channel IDs or                    the second known list of bad channel IDs based on                    the administrator mobile device app state                    designation            -   send a message to the mobile device containing the value                of the SD-App on the server.

In one variation, the order for the above, as regards at the mobiledevice, is that the channel IDs are sent to the mobile device, and thenat the device the channel IDs associated with the app are tested againsta previously-received list of good/bad channel IDs (e.g., white list 432and black list 434 of FIG. 4).

Regarding the above at the server, a channel ID associated with anindividual app is sent from MCD to the server where it is tested.

In one example, if the App-State of the app on the MCD is ‘unknown,’which will be the case if the app is not from Google Play or an Amazonstore [these are the only app stores currently filling out the valueretrieved by the Android getInstallerPackageName( ) method], then anidentifier can be sent for the app (e.g., package name or hash of theapp) to the server (e.g., side-load server 150), which may have otherinformation about the origin and channel ID of the app, and the appidentifier is used at the server to determine whether the app should betrusted or not.

In the case in which the channel ID is determined by monitoring filesystem or network activity somewhere else (e.g., on this particularmobile device, or on a different device for the same app (e.g., havingthe same application identifier), or on a server (e.g., in a VM oremulator monitoring behavior of the application)), then a channel IDcould be available at the server, and thus sending an app identifier tothe server can resolve the appropriate channel ID and the designation ofit as trusted or untrusted.

Also, there is an optional variation in which the app may have beendelivered by a good channel ID, but the app is no longer available fromthat good channel (e.g., it has been pulled by the operator of thatchannel), or the version of the app being analyzed has been replaced bya newer version of the app (e.g., an update or a vulnerability fix); ineither case, the app may be considered as having an App-State of‘untrusted’ (or in an alternative approach as having a state of‘out-of-date’).

In yet other variations of the above, a previously GOOD channel ID isnow known or determined to be BAD (e.g., by side-load server 150 oradmin server 302), and a re-evaluation of apps from that channel isperformed.

In another variation, a previously BAD channel ID is now known to beGOOD, and a re-evaluation of apps from that channel is performed.

In another variation, a previously UNKNOWN channel ID is now known to beGOOD or BAD, and a re-evaluation of apps from that channel is performed.

In another variation, an app from a channel ID previously considered tobe GOOD has been determined to be undesirable (e.g., due to malwarediscovered in the channel, or for other behavioral reasons), and as aresult the designation of that channel ID as GOOD is changed to BAD orUNKNOWN.

Use case 1.3: Testing a single downloaded app (white-listed channels andno black-listed channels)

At the mobile device:

-   -   Download the app,    -   Test the channel ID associated with the app against a first        known list of good channel IDs    -   If a match is not found        -   set the MCD-State to ‘unknown’        -   send a message containing the MCD-State, the app id and the            channel to a server        -   receive a message from the server, the message containing a            SD-MCD        -   set the MCD-State based on the received state designation

At the Server:

-   -   Receive message from the mobile device    -   If the MCD-State is ‘unknown’        -   test the channel ID associated with the app against a second            known list of good channel IDs        -   if a match is not found            -   present a message to an administrator containing the app                id and the channel ID            -   receive an administrator mobile device state designation                from the administrator            -   set the SD-MCD based on the received administrator                mobile device state designation            -   if the administrator mobile device state designation is                ‘trusted’                -   update the second known list of good channel IDs                    based on the administrator mobile device state                    designation            -   send a message to the mobile device containing the                SD-MCD

Use case 1.4: Testing all apps on the mobile device (white-listedchannels but no black-listed channels)

At the mobile device:

-   -   Receive a first known list of good channel IDs (e.g., from        side-load server 10 or admin server 302)    -   For each app to be tested        -   test the channel ID associated with the app against a first            known list of good channel IDs        -   if a match is not found            -   set the App-State on the mobile device to ‘unknown’            -   send a message containing the App-State, the app id and                the channel to a server            -   receive a message from the server, the message                containing a SD-App on the mobile device            -   if the MCD-State is not ‘untrusted’                -   set the MCD-State based on the SD-App

At the Server:

-   -   Receive message from the mobile device    -   If the App-State on the mobile device is ‘unknown’        -   test the channel ID associated with the app against a second            known list of good channel IDs        -   if a match is found            -   set the SD-App on server to ‘trusted’        -   if a match is not found            -   present a message to an administrator containing the app                id and the channel ID            -   receive an administrator mobile device app state                designation from the administrator            -   set the SD-App on the server based on the received                administrator mobile device app state designation        -   send a message to the mobile device containing the value of            the SD-App on the server.

Use case 1.5: Allowing/disallowing a single side-loaded app(white-listed channels and white-listed app authors)

At the mobile device:

-   -   Download the app,    -   Retrieve the channel ID    -   Retrieve the Signature of Authorship of the app (App-Sig)    -   Test the channel ID associated with the app against a first        known list of good channel IDs    -   Test to the App-Sig against a first known good list of        authorship signatures    -   If a match is found for either test        -   set the App-State to ‘trusted’    -   Else if a match is not found        -   set the App-State to ‘untrusted’        -   send a message containing the App-State, the App id, the            App-Sig and the Channel-ID to the server        -   receive a message from the server wherein the message            contains an SD-App        -   set the App-State based on the received SD-App value

At the server:

-   -   Receive a message containing the App-State, the App id, the        App-Sig and the Channel-ID from the mobile device    -   Test the channel ID associated with the app against a second        known list of good channel IDs    -   Test to the App-Sig against a second known good list of        authorship signatures    -   If a match is found for either test        -   set the App-State to ‘trusted’    -   Else        -   set the SD-App to ‘untrusted’    -   Send a message containing the SD-App to the Mobile Device (MCD)

In one variation of the above, the app has not been installed yet, andthe MCD is downloading the app; in order to do the next step of“Retrieve the channel ID” via the “getInstallerPackageName( )” method,the app is first installed. In an alternative approach, this processingis done before the installation proceeds (e.g., because the download isintercepted to determine a channel ID, or because there is logic in theInstallerPackage that is will determine a channel ID).

In one variation, the actions taken above are to set App-State; being“allowed/disallowed” means if “allowed” then permitting installation toproceed, and if disallowed, then either uninstalling the app if it hasalready been installed, or blocking the app from executing if the apphas already been installed. In an embodiment, the signed applicationinstallation package contains a directive that the application is onlyintended for distribution from one or more specific channels, and if theapplication has been provided via a channel that was not listed, thenthe application will not be installed.

Use case 1.6: Conditionally allowing/disallowing a single side-loadedapp

At the Mobile Device:

-   -   Download an app    -   Test the channel ID associated with the app against a first        known list of good channel IDs    -   Test to the App-Sig against a first known good list of        authorship signatures    -   If a match is found for either test        -   set the App-State to ‘trusted’    -   Else if a match is not found        -   set the App-State to ‘untrusted’        -   send a message containing the App-State, the App id, the            App-Sig and the Channel-ID to the server        -   receive a message from the server wherein the message            contains a set of conditions that are required in order for            the app to be allowed        -   present the received conditions to the user        -   receive and execute input settings from the user        -   if the settings meet the required conditions            -   set the App-State to ‘trusted’            -   send a message containing the App-State, the App id, and                indicating that the set of conditions have been                fulfilled to the server        -   else            -   send a message containing the App-State, the App id, and                indicating that the set of conditions have not been                fulfilled to the server

At the Server:

-   -   Receive a message containing the App-State, the App id, the        App-Sig and the Channel-ID from the Mobile Device    -   Test the channel ID associated with the app against a second        known list of good channel IDs    -   Test to the App-Sig against a second known good list of        authorship signatures    -   If a match is found for either test        -   set the App-State to ‘trusted’    -   Else if a conditional match is found        -   retrieve the set of conditions required for the app to be            allowed        -   send a message to the Mobile Device wherein the message            contains the set of conditions required for the app to be            allowed        -   receive a message from the Mobile Device containing the            App-State, the App id, and indicating whether or not the set            of conditions have not been fulfilled.

Various different situations associated with the above use cases mayexist. In some cases, a channel is white for all apps or black for allapps, or sometimes an admin (e.g., admin server 302) may configure amore-complicated combination. For example, a particular channel ID maybe predominantly GOOD (e.g., Google Play Store), but there may becertain known BAD apps available from that channel. In this case thechannel ID has a ‘default’ designation as GOOD, but there is a blacklist for that channel of specific apps known to be BAD, and this channelspecific list is also consulted during any decision processes (e.g., bythe admin server and/or the side-load server).

In another example, an enterprise (e.g., admin server 302) may not onlystore a list of GOOD channel IDs, but may also choose to have achannel-specific list of white-listed apps, which are the only ones fromthat channel that are to be allowed as ‘trusted.’ An example of this isthat only enterprise-approved apps are allowed from that channel and notany other channels.

Another variation involves there being multiple destinations orinstall-locations on a single mobile (or other computing) device.Specifically, each ‘container’ on a mobile device can represent aseparate install location (e.g., the ‘personal’ container and the ‘work’container), as with the Google at Work product or other containersolutions like those available from Good Technology. In this case, thedesignation of a channel as GOOD or BAD depends on the ‘installlocation’ for the app; that is, in one case, the only GOOD channel IDfor the Work container on the device is the enterprise version of theGoogle Play app store; the general consumer version of the Google Playapp store is not considered as a GOOD channel ID for the Work container.This variation may apply, for example, to any of the use cases above.

In some cases, an app appears to be available from both trusted anduntrusted channels (e.g., the app is determined to be the same app basedon a hash of each app). In these cases, if the app is identical to theapp that is available from the trusted channel, then the app state isset to trusted, otherwise it is set to untrusted. Also, side-load server150 may or may not know where the actual app installed on the device wassourced from (e.g., whether from the trusted channel or the untrustedchannel). Thus, the side-load server may choose to determine that theapp is untrusted or unknown because the actual source of the app is notknown.

Some embodiments relate to wearable apps. These are apps which run on awearable device (e.g., Android Wear), but these apps are packaged insidea handheld app, because users cannot browse and install apps directly onthe wearable itself. If packaged properly, when users download thehandheld app, a system automatically pushes the wearable app to thepaired wearable. For example, seehttps://developer.android.com/training/wearables/apps/packaging.htmlAlso see https://developer.android.com/training/building-wearables.html

There are cases of wearable apps being packaged inside the APK for thehandheld device for subsequent installation onto a wearable device. Withrespect to detection of malware, or determination of whether the app isundesired, the wearable app may be scanned using a whitelist or ablacklist or a decision component. Also, there are cases in whichwearable apps do not run on the mobile device, but instead run on apaired or connected wearable, and which are provisioned via a connectionthrough the mobile device. Here, the source identifier for the embeddedwearable app consists of the source identifier of the containing appplus the fact that the wearable app was contained within that wearableapp. The side load protection system may distinguish between thecontaining app for installation or running on the mobile device and theembedded app for installation or running on the wearable device; e.g.,one may be allowed, while the other may not, the decisions of the systemcan be independent of each other for these two apps and devices.

In one example, for an app that was preloaded on the device, the resultfrom “getInstallerPackageName( )” can be “null.” If this value returnedcannot be used to distinguish pre-loaded from non-pre-loaded apps, thesystem can determine by other attributes if the app had originally beenpre-loaded [e.g., such as if the app is installed in location/system/appor/system/priv-app (Android 4.4 or greater)].

In another example, an app's install channel is detected on the device,or is detected in a piece of code that operates somewhere in the networkpath from the install/download network source to the device (e.g., in anetwork appliance/router/firewall/etc.). For example, by observing thatan application is being downloaded to the device from a particularnetwork location, a channel ID can be determined for that application asbeing an identifier for the source of the download, e.g., a network IPaddress, or domain name, or URL, or other network identifier. In such avariation, the system may choose to not allow a network connection to anetwork location known to be a source of bad channel IDs forapplications, based on user preference, user policy or enterprise policy(e.g., as set by the admin server 302), or may choose to not allow anapplication to be downloaded from such a network source (othercommunications with this network source might be allowed).

In various cases, one detects a trusted/untrusted channel BEFORE theinstall, DURING the install, or AFTER the install. The URLhttp://developer.android.com/reference/android/content/pm/PackageInfo.htmldescribes the PackageInfo class on Android. This may be obtained fromthe getInstallerPackageName(String packageName) method in thePackageManager class. Seehttp://developer.android.com/reference/android/content/pm/PackageManager.html#getInstallerPackageName(java.lang.String)

This stackoverflow article(http://stackoverflow.com/questions/13289748/can-packagemanager-getinstallerpackagename-tell-me-that-my-app-was-installed-f)says that:

Google Play: “com.android.vending” or “com.google.play” or“com.google.android.feedback”

Amazon: “com.amazon.venezia”

Elsewhere: “null”

Samsung's installer may return com.sec.android.app.samsungapps.

The getInstallerPackageName is API Level 5 (Android 2.0+).

If the source of the information of “channel ID” is calling“getInstallerPackageName( )”, then there will typically be a non-nullanswer only for Google Play or the Amazon store or the Samsung store. A‘null’ value means an unknown channel ID—and thus is determined (atleast initially) to be an untrusted channel ID. If the actual source ofthe app can be determined as the network location or URL used todownload the app, than that network location is the source ID or channelID for the application.

In another embodiment, enterprise resources are protected when anapplication on a mobile device associated with the enterprise has beendetermined to have an application installed from an untrusted channel.In one example, a use case 2.1 relates to applying an enterprise policy(in many variations).

In this example, one or more of the following actions are taken:

At the mobile device:

-   -   access enterprise policy rules    -   follow enterprise policy rules (many possible actions or        combinations) such as:        -   present warning/notification info to the user,        -   remove untrusted app,        -   suspend access to the untrusted app,        -   instruct user to remove app,        -   provide instructions to the user,        -   suspend access to enterprise resources,        -   remove enterprise apps from the user interface,        -   disable access to enterprise apps on the mobile device,        -   suspend access to vpn (virtual private network),        -   suspend access to enterprise wifi,        -   suspend access to enterprise contact list,        -   suspend single sign on access requests,        -   present user with ability to restrict permissions for one or            more other applications,        -   transmit inventory of installed apps to a server,        -   delete enterprise content on the mobile device including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   suspend access to enterprise content on the mobile device            including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   require password to access enterprise resources,        -   remove enterprise email account from presentation on the            mobile device,        -   lock the phone,        -   locate the phone,        -   etc.

At the server:

-   -   access enterprise policy rules    -   follow enterprise policy rules (many possible actions or        combinations) such as:        -   transmit warning/notification in a message for presentation            to the user,        -   transmit message to mobile device to remove untrusted app,        -   transmit message to mobile device to suspend access to the            untrusted app,        -   transmit message to mobile device to instruct user to remove            app,        -   transmit message to mobile device to provide instructions to            the user,        -   transmit message to mobile device to suspend access to            enterprise resources,        -   suspend access of the mobile device to enterprise resources            in the network,        -   transmit message to mobile device to remove enterprise apps            from the user interface,        -   transmit message to mobile device to disable access to            enterprise apps on the mobile device,        -   suspend access of the apps on the mobile device to            enterprise resources in the network        -   transmit message to mobile device to suspend access to vpn,        -   deny vpn access requests from the mobile device,        -   transmit message to mobile device to suspend access to            enterprise wifi,        -   deny wifi access requests from the mobile device        -   suspend access to enterprise contact list,        -   transmit message to mobile device to suspend single sign on            access requests,        -   deny single sign on requests from the mobile device,        -   transmit message to mobile device to present user with            ability to restrict permissions for one or more other            applications,        -   transmit message to mobile device to transmit inventory of            installed apps to a server,        -   transmit message to mobile device to delete enterprise            content on the mobile device including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   transmit message to mobile device to suspend access to            enterprise content on the mobile device including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   transmit message to mobile device to require password to            access enterprise resources,        -   transmit message to mobile device to remove enterprise email            account from presentation on the mobile device,        -   prevent delivery of enterprise content to the mobile device,        -   etc.

In another embodiment, trust is restored between an enterprise adminserver and a mobile device that hosts an app that was installed from anuntrusted channel. In one example, a use case 3.1 relates to managedrestoration of suspended functionality.

For example, one or more of the following actions are taken:

At the mobile device or terminal:

-   -   Perform one or more of the following:        -   Restore the mobile device to factory settings.        -   Restore the mobile device memory to the state that existed            at a time that preceded the installation of the untrusted            app.        -   Receive an one or more instructions from a server and            execute those instructions on the mobile device.    -   Report the completion of all necessary actions and the readiness        of the mobile device to re-enter a ‘trusted’ state by sending a        message to a server.    -   Receive an instruction from the server to set the mobile device        to a trusted state.    -   Set the state of the mobile device to ‘trusted’    -   Restore access to enterprise resources.        -   present ‘everything is ok’ notification to the user,        -   provide instructions to the user,        -   restore enterprise apps to the user interface,        -   enable access to enterprise apps on the mobile device,        -   restore access to vpn,        -   restore access to enterprise wifi,        -   restore access to enterprise contact list,        -   restore single sign on access requests,        -   present user with ability to change permissions for one or            more other applications,        -   restore enterprise content on the mobile device including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   restore access to enterprise content on the mobile device            including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   restore single sign on access to enterprise resources,        -   restore enterprise email account presentation on the mobile            device,            At the server:    -   Receive a message from the mobile device that the completion of        all necessary actions has occurred and the mobile device is        ready to re-enter a ‘trusted’ state    -   Restore access to enterprise resources.        -   Send a message to the mobile device providing instructions            to the user,        -   Send a message to the mobile device to restore enterprise            apps to the user interface,        -   Send a message to the mobile device to enable access to            enterprise apps on the mobile device,        -   Enable enterprise apps to access enterprise resources in the            network        -   Send a message to the mobile device to restore access to            vpn,        -   Enable access to the enterprise vpn        -   Send a message to the mobile device to restore access to            enterprise wifi,        -   Enable access to the enterprise wifi        -   Send a message to the mobile device to restore access to            enterprise contact list,        -   Enable access to the network copy of the enterprise contact            list        -   Send a message to the mobile device to restore single sign            on access requests,        -   Enable access to single sign on access requests        -   Send a message to the mobile device to present user with            ability to change permissions for one or more other            applications,        -   Send a message to the mobile device to restore enterprise            content on the mobile device including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   Enable access to enterprise content on the mobile device            including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   Enable access to enterprise content on in the network            including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   Send a message to the mobile device to restore access to            enterprise content on the mobile device including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   Send a message to the mobile device to restore access to            enterprise content on in the network including            -   bookmarked web sites            -   photos            -   notes            -   documents        -   Send a message to the mobile device to restore single sign            on access to enterprise resources,        -   Send a message to the mobile device to restore enterprise            email account presentation on the mobile device,    -   Send a message to the mobile device containing an instruction        from the server to set the mobile device to a trusted state.    -   Send a message to the mobile device to present ‘everything is        ok’ notification to the user,    -   Receive a message from the mobile device confirming that the        mobile device is in a ‘trusted’ state.

In another embodiment, a determination is made as to whether anyhigh-risk activities occurred while a mobile device was in an untrustedstate due to a side-loaded application. In one example, a use case 4.1relates to an access usage log and report.

For example, one or more of the following actions is taken:

On the mobile device:

-   -   Determine the time of installation of the side loaded app        associated with the mobile device entering the ‘untrusted’ state    -   Transmit the determined time of installation of the app        associated with the mobile device entering the ‘untrusted’ state        to a server (e.g., side-load server 150 or admin server 302)    -   Determine usage parameters such as the times and durations and        quantities where appropriate of any of the following:        -   Mobile device locked while still communicating data        -   Camera on        -   Microphone on        -   Mobile device accesses or attempts to access personally            identifiable data        -   Mobile device accesses or attempts to access enterprise            resources        -   Mobile device connected via vpn or attempts to connect via            vpn        -   Mobile device connected via enterprise wifi or attempts to            connect via wifi        -   DNS resolution attempts (DNS probing by the device)        -   USB connector in use        -   Bluetooth in use        -   NFC in use        -   802.15 in use        -   Data sent to an address inside the enterprise addressing            domain        -   Data sent to an address outside the enterprise addressing            domain            -   Address is a known ‘bad’ address (e.g., location of a                CNC server or malware server)        -   Data received from an address inside the enterprise            addressing domain        -   Data received from an address outside the enterprise            addressing domain            -   Address is a known ‘bad’ address (e.g., location of a                CNC server or malware server)        -   Single sign on used to access a resource or single sign on            attempted to be used for accessing a resource.        -   Enterprise content accessed or attempted to be accessed        -   App installed or app update installed        -   Operating system or firmware update applied        -   Device hard reset performed        -   Device booted into recovery mode        -   The locations of the mobile device        -   Recording the identifiers of nearby beacons, Wi-Fi SSIDs or            BSSIDs, or Bluetooth identifiers, or other network related            identifiers        -   Switching off the mobile device        -   Switching on the mobile device        -   Removal and insertion of memory cards and sim cards        -   Use of sensors on the mobile device (part of device or            connected to device), such as biometric sensors,            accelerometer, gyroscope, magnetic sensor, proximity sensor,            temperature sensor, barometric sensor, etc.        -   Reading information from the/proc filesystem        -   Attempts to read or write information to normally protected            areas of a filesystem    -   Transmit the results of the determination of usage parameters to        a server (e.g., side-load server 150)    -   Receive an acknowledgement from the server    -   Display the determination of usage parameters on the display of        the mobile device.        At the server:    -   Receive a message from the mobile device containing the time of        installation of the app associated with the mobile device        entering the ‘untrusted’ state    -   Receive a message from the mobile device containing usage        parameters such as the times and durations and quantities where        appropriate of any of the following:        -   Mobile device locked while still communicating data        -   Camera on        -   Microphone on        -   Mobile device accesses or attempts to access personally            identifiable data        -   Mobile device accesses or attempts to access enterprise            resources        -   Mobile device connected via vpn or attempts to connect via            vpn        -   Mobile device connected via enterprise wifi or attempts to            connect via wifi        -   DNS resolution attempts (e.g., DNS probing by the device)        -   USB connector in use        -   Bluetooth in use        -   NFC in use        -   802.15 in use        -   Data sent to an address inside the enterprise addressing            domain        -   Data sent to an address outside the enterprise addressing            domain            -   Address is a known ‘bad’ address (e.g., location of a                CNC server or malware server)        -   Data received from an address inside the enterprise            addressing domain        -   Data received from an address outside the enterprise            addressing domain            -   Address is a known ‘bad’ address (e.g., location of a                CNC server or malware server)        -   Single sign on used to access a resource or single sign on            attempted to be used for accessing a resource.        -   Enterprise content accessed or attempted to be accessed        -   App installed or app update installed        -   Operating system or firmware update applied        -   Device hard reset performed        -   Device booted into recovery mode        -   The locations of the mobile device        -   Recording the identifiers of nearby beacons, Wi-Fi SSIDs or            BSSIDs, or Bluetooth identifiers, or other network related            identifiers        -   Switching off the mobile device        -   Switching on the mobile device        -   Removal and insertion of memory cards and sim cards        -   Use of sensors on the mobile device (part of device or            connected to device), such as biometric sensors,            accelerometer, gyroscope, magnetic sensor, proximity sensor,            temperature sensor, barometric sensor, etc.        -   Reading information from the/proc filesystem        -   Attempts to read or write information to normally protected            areas of a filesystem    -   Determine the level of risk based on the received messages

In one variation of the above, data has been sent that should not havebeen sent, and the amount of data and/or the frequency of such activitywas unusual or inappropriate. The actual data that is sent is capturedor inspected (or received). When inspecting such data, the administratoris notified of the findings.

In another embodiment, a population is managed in which the populationincludes mobile devices associated with an enterprise. The mobiledevices have multiple diverse apps installed from multiple diversechannels and some of those apps are determined to be side-loaded apps(e.g., determined using side-load server 150). In one example, a usecase 5.1 relates to comparing a population of interest with a controlpopulation.

For example, one or more of the following actions are taken:

At the server (e.g., side-load server 150):

-   -   Measure the proportion of mobile devices hosting an app        downloaded from an untrusted channel    -   Compare the measured proportion with similar proportions        reported for another population of mobile devices        -   If the measured proportion is sufficiently greater than the            reported proportion:            -   Send a notification of the measured proportion and the                reported proportion to an administrator (e.g., admin                server 302)            -   Receive a determination of the level of risk from the                administrator.            -   If the determined level of risk is higher than an                acceptable level of risk:                -   Revoke access to enterprise resources for all of the                    mobile devices hosting the app that was downloaded                    from an untrustworthy channel                -   Send a message to each of the mobile devices hosting                    the app downloaded from the untrusted channel                    indicating that the devices are in an ‘untrusted’                    state                -   Send instructions to each of the mobile devices for                    presentation to the user                -   Send instructions to the mobile devices per the use                    case 2.1 discussed in detail above.

In another embodiment, a determination is made of the channel or othersource for an application. In one example, a use case 6.1 relates to avalue obtained from an operating system (OS) for determining a channelID, if the ID is available. If a channel ID is not available, a channelis determined from network and/or file system activity by monitoringfile system changes.

For example, one or more of the following actions may be taken:

At the mobile device:

-   -   Monitor for changes in the file system    -   Detect a file being written which represents an application        (e.g., .apk, .ipa, etc.)    -   Determine which application is writing the file to the file        system    -   Determine which network addresses are being read from by the        application that is writing the file to the file system    -   Assign a channel ID for the detected downloaded app based on the        active network address or the application which is writing the        file to the file system

In another example, a use case 6.2 relates to determining a channel IDby monitoring network activity.

For example, one or more of the following actions may be taken:

At the mobile device:

-   -   Monitor network activity for applications    -   Detect a network transmission being read at the device which        represents an application (e.g., .apk, .ipa, etc.) (e.g., this        can be determined by an HTTP header Content-type header, or an        MIME type in the transmission (e.g.,        application/vnd.android.package-archive), or the detection of a        ‘magic number’ or file format signature)    -   Assign a channel ID for the detected downloaded app based on the        active network address from which the transmission containing an        application is coming.

At a network appliance (or server):

-   -   Monitor network activity for a mobile device,    -   Detect a network transmission being sent to the device which        represents an application (.apk, .ipa, etc.) (e.g., this can be        determined by an HTTP header Content-type header, or an MIME        type in the transmission (e.g.,        application/vnd.android.package-archive), or the detection of a        ‘magic number’ or file format signature)    -   Assign a channel ID for the detected downloaded app based on the        active network address from which the transmission containing an        application is coming.

In one embodiment, previous behavior associated with a side-loaded appon another phone is used to predict the same behavior based on the earlyindications on the subject phone.

In other embodiments, side-loaded apps are identified in various ways.In one embodiment, an origin of the app is identified, and adetermination is made (e.g., by side-load server 150) whether the app isstill available in the version that is currently being assessed (e.g.,when being considered for installation on mobile device 149).

For origin detection, some things can be done in advance; forapplications that are still available, a server checks corpus or a knownApp Store to see if the app still available there, or if a more recentversion of the same app (e.g., as determined by similarity analysis asdiscussed herein) is now available, or if the version currently beinganalyzed is no longer available.

In some embodiments regarding origin detection, when a channel ID is nototherwise obtainable, a system may determine a source or channel ID byobserving activity in a device's network connections or browser activityor file system operations. E.g., code that executes within a browser(such as a browser extension or plugin or a built-in browser function)or code that is observing the browser's activity (e.g., via monitoringof Android intents, or IOS protocol handlers, or via a network intercepton a device, such as for example a network shim or adapter or VPN or ina network appliance). Such code can detect that an app (e.g., an .apk or.ipa or other app packaging file format) is being downloaded (e.g.,looking at a URL for source, or looking at HTTP header Content-type(e.g., application/vnd.android.package-archive for an Android APK, orapplication/octet-stream for an iOS IPA file); or seeing how the filename is represented in headers if present to see that a .apk or .ipaapplication file type is being downloaded). An app whose download isdetected in this manner can be determined to be from a source or channelID of the network location or URL used for the download.

In one embodiment, it may be detected whether an app download is via aclient pull request or a web App Store push request, or an MDM app pushrequest.

In one embodiment, an app has the same hash as a version from a knownsource, but is not delivered via that source. For example, an app isdelivered via USB or Bluetooth (BT) or another peripheral form ofcommunication (e.g., an Android USB ADB interface). Or an app is or wasdelivered by some other app (e.g., a third-party App Store app).

In one embodiment regarding post-installation detection for anapplication, a server or other computing device determines a source ofthe application by visiting/going to a plurality of well-known appstores, and seeing if an app with the same hash is available fordownload there (e.g., this can include an enterprise App Store or an MDMcontrolled store). Alternatively, one can use a cache of such infoobtained previously from these source(s) (e.g., at a security companyserver); and determine that (i) an app with this hash is available therenow; or (ii) an app with this hash is not available there now, but wasavailable there in the past; and/or (iii) a newer version of the app(e.g., as determined by component analysis and/or similarity analysis asdescribed herein) is now available there. Also, in some cases, the sameapp can have been available from multiple sources.

In one embodiment, for reports to administrators or other enterprisereports, it is determined whether this app is present on any otherdevices for the enterprise (e.g., mobile devices managed by admin server302) plus numbers of devices and/or details of device activity,including present and/or historical. The prevalence of this app on anyworldwide devices may be determined, including details of app or historyor statistics of usage or behavior; and optionally determination of theprevalence among other enterprises' devices anonymized with optionalclassification of enterprise size and IR type (e.g., SAIC Code).

In one embodiment, high confidence (e.g., confidence determined to beabove a threshold) findings can be reported to an admin server,including support for a correlation of the app presence with any of:network endpoints visited; other apps present on the mobile device; orany other metadata related to device or networks connected to the mobiledevice, or user or other metadata. Also, a server can track the originas to what network(s) device the mobile device was connected to at thetime of download, or the specific computing device/network through whichthe download to the mobile device was made.

In some cases, an app is preloaded on a device. It can be determinedwhether the app has been updated since the preload time (e.g., updatedby an automatic update and/or a user-initiated update); and/or whether afirmware flash or OTA OS UPDATE has occurred.

In one variation, an indication is put inside the app (e.g., inserted bythe developer, such as by a developer server, into or with the code ofthe application) of an intended channel for delivery. The app should notshow up with a different channel ID having been determined afteranalysis (e.g., by side-load server 150). Otherwise, the app isconsidered to be from a bad source or untrusted.

In one embodiment, a change in the assessment of an app (e.g., as beingbenign, or malware, or other) may trigger a change in the assessment ofa channel (e.g., the channel through which the app was distributed). Forexample, if a channel had been hitherto determined to be unknown (vs.trusted or untrusted), then the channel assessment may be altered totrusted or untrusted.

Evaluation and Monitoring of Applications Installed on Computing Devices

As described in more detail below, a user may express an intent as tohow the user desires its computing device (e.g., mobile device 149) tobehave. The intent may be explicitly provided by the user or may beotherwise determined (e.g., by reference to a database on a remoteserver). In one embodiment, the user's intent defines how the user wantsto control receiving of certain types of messages (e.g.,advertisements). The type of control desired by the user in its variousforms of experience on a computing device (e.g., a mobile device 149) isexpressed in the user's intent. This intent may be used to determinevarious behaviors of the computing device. For example, some undesiredbehaviors may be stopped by disabling various components of one or moreapplications that have been previously installed on the user's mobiledevice.

In one embodiment, the system of FIG. 1 may be used for control ofbehavior on computing devices or for analysis of software components,each as described herein, in which user terminals and mobile devices, orother computing devices communicate with a messaging server and/orapplication marketplace 123, or with an identity server (not shown; someexamples of the identity server were discussed above), according tovarious embodiments as described below. In FIG. 1, the user terminals(e.g., 141, 143, . . . , 145) and/or mobile devices 147, 149 are used toaccess and/or communicate with side-load server 150, an identity server(not shown), application marketplace 123 (e.g., an Android or GooglePlay marketplace), and/or a messaging server (e.g., an email server)(not shown) over communication network 121.

A server (e.g., side-load server 150 or administrator server 302)receives at least one behavioral preference of the user from mobiledevice 149, and the at least one behavioral preference is determined bythe application based on input from the user. The server stores the atleast one behavioral preference for later uses such as responding toqueries from other computing devices regarding the intent of the user ofmobile device 149. In one embodiment, the server is independentlymaintained by each of many ad networks. The Ad Network Detector asdiscussed herein may manage these behavioral preferences on behalf of auser for these networks. In an alternative embodiment, an identityserver (e.g., such as was discussed above) includes a database, whichstores component identities and user policies.

In one embodiment, an application referred to herein as “Ad NetworkDetector” may be downloaded from the Google Play service onto a user'smobile device 149. The expressing of user intent and control of behaviorfor mobile device 149 as described below may be incorporated into orotherwise work in conjunction with the Ad Network Detector application.

The Ad Network Detector application scans a user's phone or tablet forthe presence of ad networks used in mobile apps, giving the userinformation about what types of ads can be displayed, and whatinformation is gathered by the ad networks. With access to thisinformation, the user is able to decide whether to keep the applicationthat has a particular ad network on the user's phone.

Mobile device (e.g., smartphone or tablet) usage has increaseddramatically, and some advertisers have begun to experiment withaggressive, new techniques to display ads on mobile devices. Thesetechniques include pushing ads to the standard Android notification bar,dropping generically designed icons on the mobile desktop, and modifyingbrowser settings like bookmarks or the default homepage. Because each ofthese techniques can display an advertisement outside the context of aspecific application, it's difficult for users to know exactly which appis responsible for any given ad. The Ad Network Detector applicationprovides a method for users to determine which ad network andapplication are the source for such ads.

Some ad networks also collect information that identifies a specificdevice or user for use in targeted marketing campaigns. Much like forbrowser-based ads, this practice allows users to see more personalizedor relevant ads. It is sometimes difficult for a user to know whataspects of the user's information are collected by ad networks. Thecapabilities and information collection methods specific to each adnetwork may be determined from investigation. The Ad Network Detectorapplication informs the user what data is being collected, and by whichad network/application.

In this embodiment, the Ad Network Detector application providesinformation to the user to about practices supporting mobileadvertising. The application may detect many ad networks. Some of the adnetworks detected may include the following examples:

-   -   LeadBolt    -   AdFonic    -   AdKnowledge    -   AdMob    -   BuzzCity    -   Casee    -   Everbadge    -   JumpTap

Regarding ad network capabilities and privacy, in this embodiment thecapabilities and information collection methods specific to each adnetwork may be investigated. Based on this investigation, the Ad NetworkDetector application details what identifying information is collectedby each ad network, and how it is collected. This may include personalinformation directly linkable to an individual user, such as an emailaddress, and device and network information that is specific to anindividual device or network, rather than to the user.

In one embodiment, a screen is presented by an installed application(e.g. the Ad Network Detector application after installation fromapplication marketplace 123) to a user on a display of mobile device149. In this embodiment, a user expresses his or her intent to controlbehavior of application components on mobile device 149.

In one example, a BTController application has previously been installedon the mobile device 149 by the user, among numerous otheruser-installed applications. The BTController includes an advertisementnetwork component having several behaviors. A first behavior is thedisplay of advertisements in the notification bar of mobile device 149.

In this embodiment, the components of each application (e.g.,BTController) previously installed on mobile device 149 are determined(e.g., determined by an application or another tool installed on themobile device for that purpose). For example, a scan to determine thesecomponents may be initiated by the user by her clicking on or touching astart scan button of a user interface.

An example of a component to be identified is the LeadBolt advertisingnetwork included in the BTController application. In addition, at leastone behavior (e.g., displaying of ads in the notification bar)associated with each of the components for an installed application isidentified.

The identified behaviors are presented to the user (e.g., in a list ofscan results). At least one behavioral preference expressing the intentof the user is determined (e.g., a desire of the user to opt out of aparticular behavior). This intent is then implemented on the mobiledevice by reconfiguring the identified components of variousapplications on the mobile device as necessary to conform to the user'sexpressed intent.

In one embodiment, a status display presented to the user by theinstalled application that indicates the status of analyzingapplications on the mobile device 149 (i.e., other applications that areinstalled on the mobile device) to identify their respective components,according to one embodiment. An extent of progress of the analysis orscan is indicated by a bar.

In one embodiment, a set of results is presented to the user from theanalyzing of the applications on the mobile device 149. The resultsinclude a list of behaviors identified. For example, one behavior is thedisplay of ads in the notification bar of the mobile device. The numberof applications identified that include a component exhibiting thelisted behavior is indicated in vertical arrangement or column.

For example, only one application was identified that includes acomponent exhibiting this behavior. Two applications were identifiedthat include a component exhibiting a different behavior. In contrast,zero applications were identified including a component that exhibitsyet another behavior. It should be noted that the count, in thisimplementation, refers to the number of components that exhibit aparticular behavior. This count (or an additional count) in otherimplementations could reflect the number of applications that exhibitthe behavior. Any given component may be present in several differentapplications, so these two counts are not necessarily equal.

In one embodiment, a screen presents information about an advertisementnetwork (LeadBolt) incorporated in an application (BTController)installed on mobile device 149. The screen includes a description of thebehavior associated with the application.

In one embodiment, a screen presents an opt-out button for the user toopt out of the advertisement network. The screen includes a descriptiondescribing an opt-out option for the advertisement network. The userexpresses her intent by clicking on or touching (e.g., on a touchscreen) opt-out button.

In one embodiment, the user's intent may be stored locally in a memoryof mobile device 149. Alternatively, this intent may be stored remotelyon a different computing device such as a server (e.g., a serveroperated by the software developer of the Ad Network Detector discussedabove) accessible via communication network 121. This server may also beaccessible by third-party application developers in order to conformbehaviors to intents previously expressed by respective users. Inanother embodiment, this server is operated by the owner of thecomponent.

Various other embodiments are now described below. In a firstembodiment, a computer-readable storage medium stores computer-readableinstructions (e.g., instructions of an Ad Network Detector), which whenexecuted, cause a computing device (e.g., a mobile device of a user) to,for an application installed on the mobile device of the user, determinecomponents of the application; identify, via at least one processor ofthe mobile device, at least one behavior associated with each of thecomponents, including a first behavior (e.g., ad display in anotification bar) associated with a first component; present resultsfrom the identifying to the user, the results to include a list ofbehaviors including the first behavior; and receive a selection from theuser of at least one behavioral preference. Further informationregarding determining the components of an application is discussed ingreater detail below in the section titled “Analyzing Components of anApplication”.

In one embodiment, the at least one behavioral preference is selectedfrom the group consisting of: opting out of the first behavior; optingout of one or more of the components including the first component; aset of user preferences for specifically-identified behaviors; and apolicy. In one embodiment, the at least one behavioral preference is apolicy, and the policy is enforced on new applications installed on themobile device. In one embodiment, the first component enables the userto selectively opt out of individual behaviors of the first component.

In one embodiment, the selection from the user of at least onebehavioral preference is to opt out of the first behavior, and theinstructions further cause, after the opting out, running the firstcomponent to determine whether the first behavior is active. In oneembodiment, the determining whether the first behavior is activecomprises at least one activity selected from the group consisting of:running the first component in an emulated environment on a differentcomputing device (e.g., a developer server); and monitoring behavior onthe mobile device after receiving the selection from the user.

In one embodiment, the selection from the user of at least onebehavioral preference is to opt out of the first behavior, and theinstructions further cause, after the opting out, determining a statusof the opting out using an application programming interface of thefirst component. In one embodiment, the instructions further cause themobile device to, in response to the selection from the user,reconfigure execution of the first component so that the first behaviorno longer occurs on the mobile device.

In one embodiment, the instructions further cause, in response to theselection from the user, uninstalling the application from the mobilecomputing device. In one embodiment, the instructions further cause, inresponse to the selection from the user, disabling further execution ofthe first component on the mobile device. In one embodiment, the firstcomponent is shared by the application and an additional application,and the disabling affects both the application and the additionalapplication.

In one embodiment, the first behavior is a presentation of messages tothe user. In one embodiment, the messages include at least oneadvertisement presented in a notification area of the mobile device. Inone embodiment, the presentation of messages is outside of a context ofthe application presented to the user during normal operation of theapplication. In one embodiment, the first component is a part of theapplication.

In one embodiment, the instructions further cause displaying opt-outoptions to the user, wherein the opt-out options are solely forapplications already installed on the mobile device. In one embodiment,the instructions further cause displaying opt-out options to the user,the opt-out options comprising all possible opt-out flows for the useron the mobile device as determined from a database. In one embodiment,the first component is a linked library packaged with the applicationprior to installation of the application on the mobile device.

In one embodiment, the mobile device is, for example, a tablet device,or an Android phone device. In one embodiment, the first component is aportion of the executable code of the application, and the executablecode enables the application to interact with an advertising network oran analytics network. In one embodiment, interaction with theadvertising network comprises display of advertisements provided fromthe advertising network.

In one embodiment, a non-transitory computer-readable storage mediumstores computer-readable instructions, which when executed, cause acomputing device to: for an application installed on a computing deviceof a user, determine components of the application; identify, via atleast one processor, at least one behavior associated with each of thecomponents, including a first behavior associated with a firstcomponent; and determine at least one behavioral preference of the user.

In one embodiment, the instructions further cause storing the at leastone behavioral preference on the computing device so that theapplication can locally determine the at least one behavioralpreference. In one embodiment, the instructions further cause the firstcomponent to evaluate the at least on behavioral preference to determinehow the first component is to behave on the computing device.

In one embodiment, the instructions further cause storing the at leastone behavioral preference on a different computing device so that anadvertisement network associated with the first component can query thedifferent computing device (e.g., a developer server) in order todetermine the at least one behavioral preference of the user. In oneembodiment, the instructions further cause the first component toexecute in conformance with results from the query of the differentcomputing device, wherein the query includes a user identifier of theuser.

In one embodiment, the instructions further cause: in response todownloading or installing the application, scanning the application toconfirm compliance with the at least one behavioral preference of theuser; and if the application violates the at least one behavioralpreference, alerting the user of the violation or blocking installationof the application.

In one embodiment, a system comprises: a display; at least oneprocessor; and memory storing instructions configured to instruct the atleast one processor to: determine components of an installedapplication; identify at least one behavior associated with each of thecomponents, including a first behavior associated with a firstcomponent; present, on the display, at least one component of theinstalled application for which a user can opt out; and receive aselection from the user of an opt-out for a first component of the atleast one component.

In one embodiment, the instructions are further configured to instructthe at least one processor to present an opt-out status to the user forcomponents for which the user has previously opted out.

In one embodiment, a method includes: for an application installed on acomputing device of a user, determining components of the application;identifying, via at least one processor of the computing device, atleast one behavior associated with each of the components, including afirst behavior associated with a first component; presenting, on adisplay of the computing device, results from the identifying to theuser, the results to include a list of behaviors including the firstbehavior; and receiving, via a user interface of the computing device, aselection from the user of at least one behavioral preference.

In one embodiment, a method includes: storing, in a memory (e.g., amemory of the developer server), a first application (e.g., the AdNetwork Detector application) comprising computer-readable instructions,which when executed, cause a mobile device of a user to: determinecomponents of a second application (e.g., BTController application)installed on the mobile device; identify at least one behaviorassociated with each of the components, including a first behaviorassociated with a first component (e.g., LeadBolt component); anddetermine at least one behavioral preference of the user; and sending,via at least one processor (e.g., microprocessor(s) of the developerserver), over a communication network, the first application for storagein a data processing system (e.g., application marketplace 123) forsubsequent installation from the data processing system onto the mobiledevice.

In one embodiment, the method further comprises communicating, via theat least one processor, with the first application after installation ofthe first application on the mobile device. In one embodiment, the dataprocessing system comprises an application marketplace. In oneembodiment, a network operator (e.g., Verizon or AT&T) controls the dataprocessing system, and the mobile device is configured to operate with acellular network operated by the network operator.

In one embodiment, a system (e.g., a developer server) comprises: atleast one processor; and memory storing a first application, which whenexecuted on a mobile device of a user, causes the mobile device to:determine components of a second application installed on the mobiledevice; identify at least one behavior associated with each of thecomponents, including a first behavior associated with a firstcomponent; and determine at least one behavioral preference of the user;and the memory further storing instructions configured to instruct theat least one processor to send the first application to a dataprocessing system (e.g., application marketplace 123) so that the firstapplication can be later installed, over a communication network, on themobile device from the data processing system.

In one embodiment, the instructions are further configured to instructthe at least one processor to communicate with the first applicationafter installation of the first application on the mobile device.

In one embodiment, a method includes: communicating, via at least oneprocessor (e.g., a processor of a software server), with an application(e.g., the Ad Network Detector application) executing on a mobile deviceof a user, the application identifying at least one behavior on themobile device, the at least one behavior associated with each of aplurality of components of a plurality of other applications installedon the mobile device, and the at least one behavior including a firstbehavior associated with a first component; receiving at least onebehavioral preference of the user from the mobile device, the at leastone behavioral preference determined by the application based on inputfrom the user; and storing, in a memory (e.g., storing in a databasedistributed among multiple database servers), the at least onebehavioral preference.

In one embodiment, the method further comprises storing the at least onebehavior. In one embodiment, the method further comprises receiving aquery from an advertisement network, associated with the firstcomponent, the query requesting the at least one behavioral preferenceof the user. In one embodiment, the method further comprises receiving,from the mobile device, an identification of the first component; andrunning, via the at least one processor, the first component in anemulated environment to determine whether the first behavior is active.

In one embodiment, the method further comprises receiving a queryregarding the at least one behavioral preference in order to determineconformance of a new application with the at least one behavioralpreference. In one embodiment, the method further comprises providinginformation in response to a request, received over a communicationnetwork, in order to evaluate the at least one behavioral preference anddetermine how the first component is to behave on the mobile device.

Additional exemplary, non-limiting details regarding variousimplementations of the above embodiments are now described here below.In one example, a user may opt-out of specific components (e.g., asdetermined using the approaches described herein). The user is presenteda list of components that the user can opt out of. The user may performopt-out actions, or these may be done automatically upon user request orselection. Then, the user may see (e.g., on a display of a mobiledevice) a status indication that the user has opted out of identifiedcomponents.

In one embodiment, there are various types of opt-out options. Forexample, a user may opt-out entirely of a component, opt-out ofparticular behaviors of a component, opt-in entirely to a component,opt-in to particular behaviors of a component, purge some or all datacollected by a component, reset an identifier used to identify the useror device to a component, or otherwise modify the component's behavioron the device or the data transferred to or from the component on thedevice.

In one embodiment, opt-out options may be displayed to a user (e.g., ona display of a mobile device) using various approaches. In a firstapproach, this is done by detecting which components are present ininstalled applications on a mobile device, and then only displayingopt-out flows for the applications are installed on the mobile device.In a second approach, input is received from a user as to whichbehaviors the user wishes to opt out of. In a third approach, allpossible opt-out flows, as determined from a database, are presented tothe user.

In one embodiment, a user selects a degree of functionality within arange from minimum optional functionality to maximum optionalfunctionality and a mobile device automatically translates that intoactions to opt in and/or out of automatically-selected behaviors.

In one embodiment, a status for opt-out may be determined in variousways. A first way uses an API provided by the vendor or developer of thecomponent to determine the opt-out status. A second way determineswhether behavior is still active by running the corresponding component(e.g., in an emulated environment on a server or by monitoring behavioron the user's mobile device).

In one embodiment, a user declares preferences for specific behaviorsdesired on the user's mobile device. The components themselves evaluatethese declared preferences in order to determine how the componentsshould behave on the user's mobile device.

For example, the user may set its preferences, and then thesepreferences are stored locally or on a remote server (e.g., a developerserver). A component queries these preferences (e.g., by sending aquery) in order to determine how the component should behave (or isrequired to behave by the mobile device or another computing device).

In one embodiment, various types of preferences that can be set by theuser relate to the following: location collection for targeted ads,notifications in a notification area of the user's device, planting ofbookmarks or icons on a device, and app tracking used to delivertargeted ads (e.g., related to determining what apps a user hasinstalled).

In one embodiment, various methods may be used for storing the userspreferences. In a first approach, a local service on a device is used,whereby applications can query the local service to determine whatpreferences a user has set.

In a second approach, a server-side service permits ad networks to querya user's preferences based on a user identifier (e.g., phone number,IMEI, Android ID, Apple UDID, or hashed/salted-hashed versions of them).

In another embodiment, preferences are declared for which behaviors auser desires. Automatic scanning or alerting is performed when anapplication that violates these preferences is downloaded or installed.

For example, upon installation, the mobile device detects whichcomponents are in an application, and determines the behaviors that areassociated with components of the application. If any of these behaviorsare disallowed, or require an alert, the mobile device may either blockthe application from installing (or notify the user to uninstall theapplication), or may alert the user that the application contains adisallowed behavior in one of its components.

Now discussing additional non-limiting examples, there are variousmechanisms that a user can use to express his or her intent. One exampleis an affirmative opt-in or opt-out for specific behaviors. For example,a user may say she does not want a specific component to track herlocation, or she does not want Google analytics to know certaininformation about her. Another might be that the user sets a preferenceindicating the desire that the user does not want any third partycomponents to have access to or view the user's location data.

In another example, an application policy may be implemented. For anyapp that has a component that performs an unidentified behavior, the AdNetwork Detector will block the app from being installed on the user'sphone or other device. These are behavior-based preferences that aremanifested in the prevention of installation for any applications thatmay contain components that express such behaviors.

In one example, when an application is running on a user's phone, itshould ask a preference service or a preference store (e.g., implementedon a software developer server) what the preference is for the user andthen respect that preference during execution. Information about userpreferences for many users may be made available in a single onlinelocation so that a component can query and respect the preferences.

Regarding determining the components that are present in an application,the application can be identified and broken into components. Afteridentification, there are various techniques that may be used todetermine the behavior of those identified components. In some cases,structural comparisons of the call graphs of components in anapplication may be examined (e.g., determining which component istalking to the operating system of the mobile device, and which aspectsof the operating system are involved). Other forms of static analysismay also be used that involve analyzing the code inside of a component.By analyzing the code, it can be determined whether the component canobtain a user's location, for example, or perform other functions. Inone example, a knowledge base may be maintained that includes a list ofcomponents that are commonly distributed online and the correspondingbehaviors of those components.

Also, dynamic analysis may be used, which is essentially running theapplication component in an emulated environment or on an actual deviceand detecting what is occurring (e.g., what services the componentconnects to or communicates with) on a computing device to determinewhether a component has a particular behavior. Additional detailsregarding determination of components and component attribution areprovided in the section below titled “Analyzing Components of anApplication”.

In one example, the user may be presented with a screen that shows theapplications installed on the user's device or the behaviors on thedevice (or even the full set of all behaviors that are possible on thedevice, even outside of the apps that the user has already installed onthe device) and what applications/components the behaviors areattributed to.

In one example, a user can opt out of specific components. The user maybe shown which components are on already her phone, or the user can sayshe does not want a certain type of behavior, and the Ad NetworkDetector only shows the user the specific network opt-outs that involvethat behavior.

In another example, the user has expressed her preferences regardingbehavior. An online preference service stores these preferences, andcomponents are required to query the service prior to installation on amobile device of the user. The service may be implemented on the mobiledevice, or on a separate server.

Additional information regarding various non-limiting examples of mobiledevices and their usage more generally, including the presenting ofinformation regarding a mobile device to a user, is described in U.S.Pat. No. 8,538,815, issued Sep. 17, 2013, entitled “SYSTEM AND METHODFOR MOBILE DEVICE REPLACEMENT,” by Mahaffey et al.; U.S. patentapplication Ser. No. 13/960,585, filed 2013 Aug. 6 (which is acontinuation of U.S. Pat. No. 8,538,815), and is entitled “SYSTEM ANDMETHOD FOR PROVIDING OFFERS FOR MOBILE DEVICES”; and U.S. patentapplication Ser. No. 14/098,473, filed 2013 Dec. 5 (which is acontinuation of U.S. patent application Ser. No. 13/960,585), and isentitled “SYSTEM AND METHOD FOR GENERATING EFFECTIVE OFFERS TO REPLACEMOBILE DEVICES,” the entire contents of which applications areincorporated by reference as if fully set forth herein.

Analyzing Components of an Application

Various additional embodiments related to component analysis andattribution (e.g., identifying and determining components of anapplication) are now set forth below. The embodiments below do not limitthe generality of any embodiments in the foregoing description.

In one embodiment, an application is a mobile application, whichcontains one or more components (e.g., a library, ad network oranalytics software development kit (SDK), or other set of code designedto work together). A component identity is information about acomponent. Examples of component identities include the following: acategory (e.g. ad network, analytics, and malware SDK), authorship (e.g.Acme, Inc., John Smith), name of a component (e.g. “AdMob”), a range ofversions or all versions of a component (e.g. AdMob 6.x, AdMob, zlib),and a particular version of a component (e.g. zlib 1.2.7, AdMob SDK6.0.1). The data associated with a given component may be stored in adatabase.

In one embodiment, a component's behavior is generally that behaviorexisting or occurring (e.g., functions performed) when a component isfunctioning on a computing device (e.g., functioning in an applicationrunning on mobile device 149). One example of a behavior is the sendingof certain types of data to a server (e.g., sending browser history to aserver at www1.adcompany.com, or sending a location to a server attracking.analyticscompany.net). Other examples include the following:accessing data on a computing device (e.g., contacts, call history); andperforming certain functions on a device (e.g., changing brightness of ascreen, sending a text message, making a phone call, pushingadvertisements into a notification bar).

In one embodiment, a component's structure is how a component isimplemented in code. This structure may include a code package and/or acode module structure. Also, a component's structure may includecharacteristics of the executable code of the component, such as forexample, cross-references in a control flow/call graph, references tostatic data, and machine instructions used.

Various further embodiments related to component analysis are nowdescribed below. In a first embodiment, a non-transitorycomputer-readable storage medium stores computer-readable instructions,which when executed, cause a system to: for an application installed ona computing device (e.g., mobile device 149) of a user, determinecomponents (e.g., components 104 and 106) of the application; andidentify, via at least one processor, at least one behavior (e.g.,sending device location to an ad server) associated with each of thecomponents, including a first behavior associated with a firstcomponent. The instructions may cause the system to present, on a userdisplay of the computing device, an identification of the components.The instructions may cause the system to determine at least onebehavioral preference of the user.

In one embodiment, the instructions cause the system to store a userpolicy (e.g., user policy 108 or one of user policies 116) based atleast in part on the at least one behavioral preference (e.g., userintents expressed by the user on a mobile device), and to enforce theuser policy on new applications installed on the computing device.

In one embodiment, the instructions cause the first component to executein conformance with results from a query of an identity server (e.g.,the identity server as described earlier above, or another computingdevice). The instructions may cause the system to, in response toinstalling the application, scan the application to confirm compliancewith a user policy of the user, where the user policy is stored on theidentity server. In one embodiment, the instructions may cause thesystem to enforce, based on identified behaviors associated with thecomponents, a user policy for each of the components.

The instructions may cause the system to compare permissible behaviorsin the user policy for the components with the identified behaviors. Inone example, the comparing of the permissible behaviors comprisesdetermining behaviors, observed for the components on other computingdevices, from a data repository (e.g., a database). The instructions maycause the computing device to, in response to the determining thebehaviors from the data repository, configure or disable execution ofone or more of the components on the computing device.

In one embodiment, a system includes: a data repository (e.g., adatabase) storing component data for known components, the componentdata including data for a first known component; at least one processor;and memory storing instructions, which when executed on a computingdevice, cause the computing device to: for a new component in a firstapplication for a computing device of a user, perform a comparison ofthe new component to the component data; and based on the comparison,make a determination that the new component corresponds to the firstknown component.

In one embodiment, the instructions further cause the computing deviceto, in response to the determination, perform at least one of: comparinga first known behavior of the first known component to a user policy ofthe user; and comparing an observed behavior of the new component to theuser policy. In one embodiment, the component data includes componentidentities, each component identity corresponding to respectiveidentifying information for a known component. In one embodiment, thedetermination is made prior to installing the new component on thecomputing device.

In one embodiment, the instructions further cause the computing deviceto associate a similarity value (e.g., a value within an arbitrary rangeof zero to one) with the comparison, and wherein the determination ismade in response to the similarity value being greater than a thresholdvalue. In alternative embodiments other forms of comparison of thesimilarity value to a threshold may be done (e.g., where the similarityvalue is lower than the threshold). In one embodiment, the comparison isbased at least in part on a structure of the new component, thestructure selected from the group consisting of a packaging structure, amodule structure, and an executable code structure.

In one embodiment, the component data includes known structuralcharacteristics and known behavioral characteristics. In one embodiment,the performing the comparison comprises comparing the known structuralcharacteristics and the known behavioral characteristics to identifiedcharacteristics of the new component.

In one embodiment, the instructions further cause the computing deviceto generate a notification when the identified characteristics aredetermined to differ from at least one of the known structuralcharacteristics and the known behavioral characteristics. In oneembodiment, the generating the notification comprises sending an alertto the computing device.

In one embodiment, a method includes: storing, in memory, component datafor known components, the component data including data for a firstknown component; for a new component in a first application for acomputing device of a user, perform, via at least one processor, acomparison of the new component to the component data; and based on thecomparison, make a determination that the new component corresponds tothe first known component.

In one embodiment, the new component is selected from the groupconsisting of code from the first application, and a library in thefirst application. In one embodiment, each of a plurality of differentapplications includes the new component, the new component correspondsto a set of behaviors when executed on a computing device, and thecomponent data comprises behavioral data including the set of behaviors.

In one embodiment, the method further comprises associating the set ofbehaviors with the new component. In one embodiment, each of a pluralityof computing devices has been observed when running a respective one ofthe different applications, and each of the plurality of computingdevices exhibits the set of behaviors. In one embodiment, thedetermination is based in part on a context of operation of the newcomponent on the computing device.

In one embodiment, the context is an accessing, during execution of thefirst application, of location information while the first applicationhas a visible presence to a user (e.g., the first application ispresenting location information to the user on a user display), and theset of behaviors includes determining a location of the computingdevice. In one embodiment, the component data includes a plurality ofcontexts each associated with at least one acceptable behavior. In oneembodiment, the component data includes risk scores for knowncomponents, and the method further comprises providing a risk score inresponse to a query regarding an application installed or to beinstalled on the computing device of the user.

In one embodiment, a method comprises: storing, in memory, a firstapplication comprising computer-readable instructions, which whenexecuted, cause a mobile device of a user to: for a new component of asecond application installed on the mobile device, perform a comparisonof the new component to component data for known components, thecomponent data including data for a first known component; and based onthe comparison, make a determination that the new component correspondsto the first known component; and sending, via at least one processor,over a communication network, the first application for storage in adata processing system for subsequent installation from the dataprocessing system onto the mobile device.

In one embodiment, a system includes: at least one processor; and memorystoring a first application, which when executed on a mobile device of auser, causes the mobile device to: for a new component of a secondapplication installed on the mobile device, perform a comparison of thenew component to component data for known components, the component dataincluding data for a first known component; and based on the comparison,make a determination that the new component corresponds to the firstknown component; and the memory further storing instructions configuredto instruct the at least one processor to send the first application toa data processing system so that the first application can be laterinstalled, over a communication network, on the mobile device from thedata processing system.

Now discussing a component analysis process for one particularembodiment, a new application may be decomposed into identifiablecomponents. An identity of each component may be displayed to the user.Behavioral and/or structural characteristics attributable to eachcomponent identity may be identified. The behavior for a given componentmay be displayed to the user.

A user policy (e.g., user policy 108) based on component behavior may beenforced on the user's computing device. For example, the user policymay require that there be no applications that send location to anadvertising network. In another example, the user policy may requirethat no applications send identifiers to an advertising network.

Behavioral and/or structural characteristics of a component present inthe new application may be identified. This may be, for example, anapplication 1013 that has been installed on mobile device 149.

A comparison is made between the characteristics attributable to thecomponent identity and the characteristics that have been identified inthe new application. In one embodiment, if the identifiedcharacteristics are different from the characteristics attributable tothe component identity, then an alert is generated to indicate that thebehavior of the component has changed. The characteristics attributableto the component identity may be stored in a database of the identityserver (which was discussed above) and may be accessed when making thiscomparison. For example, these attributable characteristics may bestored as component data associated with respective component identities(i.e., known data regarding component behavior or other characteristicsof a component may be stored for each component identity).

Now, further detail regarding how component analysis is performed isdescribed below. As mentioned above, an application is decomposed intoidentifiable components. In particular, a data repository stores a setof component identities in a database.

Each component identity has identifying information for a givencomponent that, if present in an application, indicates that the givencomponent is present in the application. Examples of identifyinginformation include the following: a package name prefix for a set ofone or more classes, a class name, or a code fingerprint of a codeblock, method, class, package, etc.

When used, fingerprinting can be performed in a variety of ways. A firstway is the creating of an abstract representation of an instruction set.Another way is to, from an abstract representation, create a set ofn-gram indices that can create a fingerprint identifier for a set ofcode (e.g., a hash of indices) or that can be compared to another set ofindices to perform a fuzzy match. In yet another way, asset or resourcefingerprinting may be used. As a final way, fingerprinting may be doneby analyzing the network traffic generated by an application on a deviceor in a dynamic analysis system. Server communication, network trafficdestined to a server, may be used to associate a component with aparticular network service. Some examples of network traffic includetraffic to server with name server1.somewhere.com, traffic to serverwith IP 8.8.8.8 or 2001:4860:4860::8888, HTTP request with header“User-Agent: MyHttpLibrary-1.1”, HTTP request with a particular URI orURI pattern, and traffic that matches a SNORT or YARA rule.

Analysis of a new application can be used to determine if identifyinginformation for a given component identity matches the new application.If it matches, then the given component is present in the newapplication. This analysis can be done at the client (e.g., mobiledevice 149), the server (e.g., the identity server discussed above), orusing a combination thereof.

In one embodiment, the analysis is done at one computing device (e.g.,either on the client or the server). The database of identifyinginformation is stored locally on the computing device. The newapplication is also present locally (e.g., the new application itselfhas been previously sent to the identity server from mobile device 149,or from application marketplace or developer server 160 prior toinstallation on mobile device 149).

In this embodiment, there are multiple options for analysis. In a firstoption, for each item of identifying information in the database, thenew application is searched to determine if the identifying informationmatches the new application. Alternatively, information can be extractedfrom the new application, and then a check or comparison done to see ifthat information matches any of the identifying information stored inthe database.

In another embodiment, a client submits information to a server todetermine components that are present in an application. The database ofcomponent identifying information (known component data) is stored onthe server. The application is present on the client. The clientextracts information (e.g., component identifying information) from theapplication, and then sends this extracted information to the server.

The server checks to see if the extracted information matches any of theidentifying information in the database (e.g., the extracted informationmay be received as a query from mobile device 149). If so, the serversends back information about component identities to the client (e.g.,the server sends results from the query to mobile device 149).

In a different embodiment, the client submits an identifier for the newapplication to a server. This identifier may be, for example, a hash ofthe application binary code, a package name, a title of the application,or another form of application identifier. This server stores dataregarding previously-analyzed applications. This data includes a list ofcomponents for each of the previously-analyzed applications. In yetother embodiments, the application information is gathered from anapplication store or marketplace, or from another device different fromthe client (e.g., where the application is not installed on a client,but is stored within an application store for downloading andinstallation, or is being staged for placement into an applicationstore). Information from or about the application may be gathered fromthe application store or marketplace, or such other device. U.S.Publication No. 2012/0240236, filed 2010 Aug. 25, entitled “CrawlingMultiple Markets and Correlating,” is incorporated by reference as iffully set forth herein. U.S. Publication No. 2012/0240236 is acontinuation-in-part of U.S. Pat. No. 8,533,844, entitled “System andMethod for Security Data Collection and Analysis.”

The server of the different embodiment above uses the identifierreceived from the client and compares this identifier to the dataregarding previously-analyzed applications. If there is a match betweenthe identifier and a previously-analyzed application, then thecomponents for that matched application (obtained from the stored listof components above) are determined to be in the new application (andthis result may be sent to the client). This matching to the databasemay be done similarly as was described earlier for the componentanalysis above. The server of the different embodiment above sendsinformation about these identified component identities back to theclient.

After a component has been identified as being present in anapplication, the identity of the component may be displayed to the user.For example, identification and display of components present in anapplication may be done similarly as was described above for the AdNetwork Detector. Behavioral and/or structural characteristics that areattributable to a given component as stored in the database for variouscomponent identities may be sent from the server to the client for thosecomponents that have been identified as being present in an application.

In one embodiment, there are various ways to identify characteristicsthat are actually present in a component of an application. For example,U.S. Pat. No. 8,533,844, issued Sep. 10, 2013, and entitled “System andMethod for Security Data Collection and Analysis”, by Mahaffey et al.;U.S. patent application Ser. No. 13/958,434, filed 2013 Aug. 2, entitled“ASSESSING A DATA OBJECT BASED ON APPLICATION DATA ASSOCIATED WITH THEDATA OBJECT”; and U.S. patent application Ser. No. 14/688,292, filed2015 Apr. 16, entitled “System and Method for Assessing an ApplicationBased on Data From Multiple Devices,” which applications areincorporated by reference as if fully set forth herein, provide ageneral discussion about the gathering of information from anapplication on a mobile device for further processing at a server.According to this embodiment, information that has been gathered asdescribed by Mahaffey et al. in U.S. Pat. No. 8,533,844 is then used forcomponent analysis at the identity server (discussed above) in order toidentify characteristics of a component.

In another embodiment, behavioral characteristics may be determined orcollected using other approaches. For example, behavior may bedetermined based on network traffic (e.g., SMS, IP) data, or based onthe code source of a given behavior (e.g., a class name or a packagename responsible for geo-locating, or a fingerprint of a code segmentresponsible for sending SMS traffic).

In one embodiment, component identity-attributable characteristics arecompared to actually-present characteristics (e.g., as gathered for anew application just installed on a mobile device). For example, ifbehavior is part of the known data for a component identity, and a newapplication's component behavior matches this known behavior, then it isassumed that information about the component identity applies to the newapplication. Information about the component identity may include, forexample, a text description, risk scoring, and data whether anapplication is malware or is not malware. For example, this informationmay be provided as a result or response to a query from a mobile device.

If the actual behavior and the known behavior for the component identityare different, this may indicate that the component in the newapplication is a newer version or a tampered-version, and that thecomponent needs to be reviewed again in order to update the database.Also, an alert may be generated based on the component informationdetermined above. For example, an email may be sent to an analyst to dofurther analysis of a component, or an entry may be created in a workqueue regarding further component analysis to be done.

In various other embodiments, the results from component identificationfor applications on a device are presented to the user. The user mayprovide input in a user interface to define or update a user policybased on this component identification. For example, the user mayopt-out of an identified component.

In another embodiment, a component review process is provided forreviewing potentially undesirable code at scale (where manual review isnot practical). The component analysis as described above is automatedso that a human is not required to do component analysis manually.Characterizing components that have been previously reviewed (e.g.,stored as data for a component identity with a risk score) anddetermining when that component has changed behavior (i.e., the actualbehavior is different from the known behavior stored in the componentidentity) can create an automated process where humans only need tore-review component code when its behavior has changed. A behaviorchange may also be associated with a code fingerprint having changedslightly (e.g., if doing a fuzzy match, there is a threshold for whichit is considered that there is no change, and another threshold forwhich it is considered that that there is a sufficient change inbehavior). In various embodiments a comparison to a threshold may bedone to see if a value is lower or greater than the threshold (which mayinclude the cases of equal to or lower, or equal to or higher than thethreshold). Similarly, other characteristics disclosed can be used todetermine if the component in the new application exactly matches theknown component or if it partially matches in a way that meritsre-analysis.

Yet another embodiment relates to behavioral risk analysis ofapplications. In this embodiment, the component analysis involvesseparating identified components that have already been reviewed (i.e.,components that have known component data stored in a database), andthat are common across numerous different applications (or across copiesof the same application) as installed on many computing devices, fromcomponents that are unique (e.g., an associated behavior has not beenobserved before) to a particular new application (e.g., behavior uniqueto a single, most-recent installation on mobile device 149). Theseunique behaviors are specifically audited within the context of the newapplication (e.g., application 1013).

As an example of context, it is common for ad networks to ask forlocation data. This is a well-accepted behavior. If a user is looking,for example, at a game like Angry Birds, an application that asks for alocation may be exhibiting acceptable behavior if this behavior isassociated with an ad network that has been previously observed as beingacceptable (e.g., as determined from data stored in a database).However, in other cases, actual game code that is itself asking forlocation may be inappropriate behavior.

The amount of code that is unique to any given application is typicallyfairly small. Most applications (e.g., for mobile devices) predominantlyuse code that is in at least one or many other applications (themajority of code in an application is typically not unique and there isa lot of commonality in code between applications).

Sometimes, when a behavior is analyzed in the context of a known SDK,the behavior is a repeatable behavior that has previously beendetermined to be acceptable (or to have a low risk score). Thus, forexample, if a library has already been reviewed, then further analysiscan be skipped.

In an embodiment regarding similarity of known and new applications,fuzzy matching and fingerprinting may be used (as was discussed above).For example, a similarity score of zero to one may be used. A similarityscore is returned from the server after analysis of a new application.The code in the new application is compared to code that is already inthe identified component library (e.g., a library in a database on theidentity server that was discussed above).

Typically, there is not an exact code similarity match because there aremany changes that a compiler can make to a particular applicationinstallation to make it different than other installations. Similaritiesare defined so that if the differences are over a similarity threshold,then a determination is made that a known component is present in thenewly-installed application. For example, the new application mayinclude a slightly-customized version of a component (that waspreviously determined to be acceptable). In alternative embodimentsother forms of comparison to a threshold may be done (e.g., where avalue is lower than the threshold). In other cases, the new applicationmay include a new version of a component that has not been previouslyanalyzed. In one embodiment, unacceptable code that has been onlyslightly modified to defeat similarity protection mechanisms is insteaddetected as unacceptable based on behavioral observation and componentanalysis as discussed above.

In one embodiment, components are analyzed with respect to similarity ofpreviously known components. Behaviors can include use of personalidentifying information or device information, or any actions that canbe taken by applications on the device, including user interfacedisplays, notifications, network communications, and file reading orwriting actions. Policies to control or restrict the behavior ofapplications and their components may be defined and applied. This caninclude the identification of advertising networks and defining policiesto permit various opt-out actions for these advertising networks.

Assessing Application Authenticity

Various embodiments related to assessing application authenticity arenow set forth below. In one embodiment, a method includes: evaluating(e.g., by a server or a mobile device) authenticity of a firstapplication (e.g., software being downloaded to a mobile device) toprovide a result, where the evaluating uses a plurality of inputs. Inresponse to the result, an action is performed on the computing device.

In one embodiment, the result is a determination of a source ofsoftware. In another embodiment, the result is a state designation thatis sent to side-load server 150 for use similarly as described above forthe administrator state designation. State designations from theauthenticity server 1005 and the administrator server may both be usedby side-load server 150 in its determination of the state designation tosend to mobile device 149.

In one example, the evaluating may be done by a server for anapplication that a user of a mobile device desires to install from anapplication marketplace. In one embodiment, the computing device is aserver, and the action is sending a notification from the server to themobile device, the notification including an assessment of authenticityof the first application.

In one embodiment, the computing device is a mobile device on which thefirst application is being or has been installed, and the action isproviding of a notification in a user interface of the mobile devicerelating to an assessment of authenticity of the first application. Inan alternative embodiment, the application may have been previouslyinstalled on the mobile device, but the user desires an evaluation ofauthenticity (e.g., to consider whether to remove the application fromthe mobile device).

In one embodiment, one or more of the plurality of inputs may bereceived from a distributor of the first application, an onlineapplication store, a carrier/operator/device manufacturer (e.g., forpreloaded software on a mobile device), and/or from a computing devicewithin an enterprise or an organization's internal network.

In one embodiment, the computing device is a server (e.g., authenticityserver 1005), and the first application has a first package identifierand a first signing identifier, the method further comprising receivingthe first package identifier and the first signing identifier from amobile device on which the first application is being or has beeninstalled. The first package identifier may be, for example, an Androidpackage name, an Apple iOS bundle identifier, or a hash of such name oridentifier, etc. The first signing identifier may be, for example, acertificate (e.g., a signing certificate, digital certificate, etc.), acertificate thumbprint, or a public key, or a hash of a certificate, ahash of a public key, or other data which can be used to identify thesigner. In one embodiment, the method further comprises receiving thefirst application itself from the mobile device (e.g., for testing orother operation for evaluation by the server).

In one embodiment, the plurality of inputs comprises receipt (e.g., froma computing device of a developer of the first application) of adeveloper signing certificate for the first application, and theevaluating comprises comparing the developer signing certificate to thefirst signing identifier.

In one embodiment, the plurality of inputs comprises one or more of thefollowing: receipt, from a computing device, of an indication ofownership in the first application by a developer (e.g., a developer ofknown or assumed credibility simply makes an assertion or claim toownership in an electronic communication); a prevalence of the firstapplication (e.g., the application is the most popular version that hasbeen distributed and this version is assumed to be authentic); and amodel (e.g., a model to predict expected characteristics associated witha first application and/or to assess observed behavior orcharacteristics for the first application). In one embodiment, the firstapplication has a first signing identifier, and the plurality of inputscomprises a history of the first signing identifier.

In one embodiment, the method further comprises comparing a firstsigning identifier of the first application to a signing key in aregistry of known signing keys. In one embodiment, the registrycomprises a plurality of package identifiers, each identifier associatedwith a respective one of the known signing keys, and the method furthercomprises comparing a first package identifier of the first applicationto the plurality of package identifiers.

In one embodiment, the result from the evaluating is a score, and theperforming of the action is conditional on the score exceeding athreshold (or other alternative forms of comparison to the threshold).

In one embodiment, the evaluating comprises: identifying a plurality ofapplications that are similar to the first application (e.g., usingcomponent analysis as discussed above); classifying the similarapplications, based on a respective signing identifier for eachapplication; and identifying, based on the classifying, applicationshaving a signing identifier of a developer, and applications having asigning identifier that is different from the signing identifier of thedeveloper.

In one embodiment, the method further comprises sending a notificationto a computing device of the developer that identifies the applicationshaving the signing identifier that is different from the signingidentifier of the developer.

In one embodiment, the identifying the plurality of applications thatare similar to the first application comprises identifying applicationshaving at least one of an identical package identifier, code similarity,identical strings, similar strings, identical media assets, and similarmedia assets. In one embodiment, a server determines the similarity ofnewly-observed applications to a previously known-to-be authenticapplication (e.g., stored in a database at the server). In one example,this determination includes component analysis (e.g., comparison ofknown and new components) and/or application/component/code similarityassessment as was discussed earlier above. In another example, theserver can notify the developer of the authentic application, orchallenge the developer to authenticate itself as the actual applicationsigner for the newly-observed application(s).

In one embodiment, the method further comprises receiving the signingidentifier of the developer, sending data to the developer to be signedby the developer with a private key, receiving the signed data from thedeveloper, and confirming the signed data corresponds to the signingidentifier of the developer. For example, the data sent to the developermay be an archive or a nonce, or the data may be for the issuing of acrypto-based challenge to the developer.

In yet another embodiment, the first application may be examined in thecontext of known business entity databases (e.g., Equifax database, Dun& Bradstreet database, etc.) or other information sources, andinformation obtained from such sources may be used as one or more of theplurality of inputs in the evaluating of the first application. Forexample, these inputs may include: the company name as determined from aWHOIS response; the name of an owner of the IP space that the firstapplication talks to (e.g., an inquiry can be made as to who owns theapplication server that the first application communicates with); theresponse to an inquiry as to whether the package name for the firstapplication corresponds to a valid organizational domain name, andfurther whether that domain name's WHOIS name shows up in a businessdatabase; and the developer name as determined in an online applicationstore such as Google Play.

In one embodiment, authenticity is assessed by a method in which mobiledevice 149 of a user communicates with authenticity server 1005 toevaluate the authenticity of new application 1013, for example which isbeing newly-installed on the mobile device (or alternatively has alreadybeen installed), according to one embodiment. In other embodiments, someor all of the authenticity functions described for authenticity server1005 may be performed by an identity server (not shown), which wasdiscussed above with respect to component analysis.

Authenticity server 1005 receives from mobile device 149 a packageidentifier and a signing identifier associated with new application1013. Authenticity server 1005 uses a plurality of inputs, such as aredescribed herein, to evaluate the authenticity of new application 1013.This evaluation provides a result, for example a score indicating therisk of the new application being inauthentic. Based on this result, anaction is performed by authenticity server 1005. If the score is above athreshold, the application may be deemed as being untrusted, or a statedesignation of untrusted may be sent to side-load server 150.

In one example, this action is the sending of a notification to a mobiledevice 149 in order to alert the user that the new application 1013 maybe fraudulent or a tampered version. New application 1013 may have beenprovided, for example, to application marketplace 123 or directly tomobile device 149, by developer server 160, along with a signingcertificate 162. Developer server 160 also provides a package identifierfor new application 1013. Signing certificate 162 is one form of signingidentifier that may be provided to authenticity server 1005 forevaluation of new application 1013.

Authenticity server 1005 has a database 1007 for storing information anddata regarding applications, such as previously known or identifiedapplications that are considered to be authentic. The authenticdeveloper or other source of the application is stored in database 1007.Database 1007 further may include component data 1009, which correspondsto information about software components as was discussed earlier above.Database 1007 further may include repository 1003, which stores packageidentifiers and corresponding signing identifiers, for example such ascollected or identified for previously authentic, known-good, or deemedgood applications.

The evaluation of authenticity may alternatively be performed in part orfully on mobile device 149. If an inauthentic application is discovered,then the user of mobile device 149 may be notified on a display of auser interface. This notification may include an assessment of theauthenticity of the new application 1013.

In one embodiment, authenticity server 1005 compares signing certificate162 to an existing signing identifier contained in repository 1003.Authenticity server 1005, in one example, compares signing certificate162 to a known, good signing key stored in repository 1003.

Various other non-limiting embodiments are now described below. In afirst embodiment, authenticity server 1005 has a registry of knownapplication signing keys and the package names they are registered for.If an application pretends to own one of those package names with adifferent signing key, a user is alerted that the application is likelytampered with. In some cases, authenticity server 1005 may also usesimilarity detection (e.g., similarity analysis as was discussed earlierabove) to determine that, even if an application has a different packagename, it is highly similar to another previously-known application, buthas a different signer.

In one embodiment, all applications are identified that are similar to agiven application (e.g., where the given application is beingnewly-installed on a mobile device). One or more of the following inputsmay be used in evaluating the new application: whether applications havethe same package name, code similarity between the applications, similaror identical strings (especially strings that occur infrequently)between new and known applications, and similar or identical mediaassets (e.g., images, sounds, video, etc.) between new and knownapplications. In some embodiments, similarity and/or component analysisas was discussed above may be used.

In one embodiment, applications that have been determined to be similar(e.g., as described above) are classified based on signing certificates,which are used to classify applications into two groups: applicationswith a given developer signing certificate, and applications with adifferent signing certificate. This classification is used for one ormore of the following: identifying potentially pirated applications(e.g., for copyright enforcement); identifying potentially maliciousapplications; optimizing a sales strategy (e.g., such as identifyingadditional markets where an application could be sold); and managingrelease processes (e.g., identifying versions of an application that aresold in different markets).

In one embodiment, a workflow for establishing ownership of a signingcertificate includes: a developer or other user uploads the certificate,then receives download of a jar (or Java archive), which the developermust sign to prove that it has the private key corresponding to thecertificate. In one embodiment, the workflow is extended to allow adeveloper to manage multiple signing certificates.

In one embodiment, a workflow for discovering applications, based onproof of certificate ownership includes: a developer or other userproves certificate ownership, then authenticity server 1005 finds allpackages signed with the same certificate, and also identifies similarapplications, signed both by the same certificate and othercertificates. In one embodiment, the workflow is extended to allow adeveloper to manage multiple signing certificates.

In an alternative embodiment, authenticity server 1005 providesmonitoring and security services to Android or other system developers.These services determine developer identification (to confirm that thedeveloper is who it purports to be). The services may include monitoringtools and/or anti-piracy functions. If the developer's application hasbeen pirated and is being distributed in different markets, authenticityserver 1005 notifies the developer.

The services may also include brand protection. For example, a bank maywant to know if a version of its application has been pirated and isbeing misused for phishing. In one embodiment, the services includelooking at actual software assets being used in applications (e.g.,logos, images, etc.) to determine if they are being used innon-sanctioned manners. Application assessments and/or reports for theabove services may be provided to a brand owner, developer, or otherentity. In another example, a vendor of application components (e.g.,such as advertising SDKs, sensor activity SDKs, etc.) may want to knowif a version of its components are being used in an application. In oneembodiment, the services include looking at application components beingused in applications (libraries, SDKs, components, etc.) to determinethat they are being used in sanctioned or non-sanctioned manners.Application assessments and/or reports for the above services may beprovided to a vendor or developer or distributor of such applicationcomponents or other entity.

In one embodiment, an assessment of privacy is provided by the services.This includes analyzing potential privacy issues in the application.Authenticity server 1005 may generate a privacy policy for the developerbased on permissions provided by the developer. In one embodiment, asecurity assessment is provided by the services. Authenticity server1005 analyzes potential security vulnerabilities and providesrecommendations to the developer or other entity.

In one embodiment, the services above permit a developer to develop agood reputation. For example, an application/developer certification maybe provided to a user after an evaluating of authenticity of anapplication. For example, a seal of approval or other visual indicationmay be provided in a user interface display for this purpose to indicateto a user that an application is authentic. The services above may besupported by analysis of application components as described above(e.g., when providing piracy or brand protection).

Additional information regarding various non-limiting examples ofanalyzing, characterizing, and/or scoring applications with respect tosecurity is described in previously-published U.S. Patent PublicationNo. 2011/0047594, published Feb. 24, 2011, entitled “System and Methodfor Mobile Communication Device Application Advisement,” by Mahaffey etal., and also in previously-published U.S. Patent Publication No.2013/0263260, published Oct. 3, 2013, entitled “System and Method forAssessing an Application to be Installed on a Mobile CommunicationDevice”, by Mahaffey et al., the entire contents of which applicationsare incorporated by reference as if fully set forth herein.

In particular, U.S. Patent Publication No. 2013/0263260 describes asystem that checks for harmful behavior of an application to beinstalled on a mobile device. A server computer receives from the mobiledevice data pertaining to the application to be installed andinformation pertaining to the mobile device. The server processes thedata and information to determine an assessment for the application tobe installed. The assessment is provided to the mobile device and theassessment is displayed on the device if the assessment is one ofdangerous and potentially dangerous. The data and information receivedfrom the mobile device may be used, for example, as one or more inputsin the plurality of inputs for evaluating the first application asdescribed herein.

Also, in particular, U.S. Patent Publication No. 2011/0047594 describesa system for providing advisement about applications on mobile devicessuch as smartphones, netbooks, and tablets. A server gathers data aboutmobile applications, analyzes the applications, and produces anassessment that may advise users on a variety of factors, includingsecurity, privacy, battery impact, performance impact, and networkusage. The disclosure helps users understand the impact of applicationsto improve the experience in using their mobile device. The disclosurealso enables a server to feed information about applications to otherprotection systems such as application policy systems and networkinfrastructure. The disclosure also enables advisement aboutapplications to be presented in a variety of forms, such as through amobile application, as part of a web application, or integrated intoother services via an API. The data gathered by the server may be used,for example, as one or more inputs in the plurality of inputs forevaluating the first application as described herein. Also, some of theforms of advisement discussed may be used, for example, in providingnotifications to the user and/or to developers or others regardingevaluations of software authenticity.

Additional information regarding various non-limiting examples of someanalytic methods for determining application behavior is described inU.S. patent application Ser. No. 14/063,342, filed Oct. 25, 2013,entitled “System and Method for Creating and Assigning a Policy for aMobile Communications Device Based on Personal Data,” by Timothy MichealWyatt, the entire contents of which application is incorporated byreference as if fully set forth herein. For example, one or more of themethods for determining behavior may be used when evaluating applicationauthenticity as described herein.

Additional information regarding various non-limiting examples ofsecurity evaluation and scoring relating to a plurality of trust factorsis described in U.S. patent application Ser. No. 14/072,718, filed Nov.5, 2013, entitled “Method and System for Evaluating Security for anInteractive Service Operation by a Mobile Device,” by Derek Halliday,the entire contents of which application is incorporated by reference asif fully set forth herein. For example, some of the trust factors may beused as inputs when evaluating application authenticity.

In one specific example, the context in which a signing certificate orother signing identifier or signing is observed is assessed usingfactors which may include one or more trust factors as described in U.S.patent application Ser. No. 14/072,718 above. These factors may, forexample, be used in formulating a score that is compared to a thresholdthat is used to make a decision whether to perform an action in responseto evaluating an application (e.g., various forms of comparison to thethreshold may be used, as described previously).

In particular, U.S. patent application Ser. No. 14/072,718 describes amethod for evaluating security during an interactive service operationby a mobile device that includes launching, by a mobile device, aninteractive service configured to access a server over a network duringan interactive service operation, and generating a security evaluationbased on a plurality of trust factors related to a current state of themobile device, to a security feature of the application, and/or to asecurity feature of the network. When the security evaluation isgenerated, an action is performed based on the security evaluation. Insome examples, these actions may be performed in response to the resultfrom an evaluation of application authenticity.

In another embodiment, the first application is evaluated to determineits components and/or to identify behaviors associated with each of thecomponents. This evaluation may provide some or all of the plurality ofinputs used in the evaluating of the first application as was discussedabove. In one embodiment, the components of the first application can beanalyzed regarding similarity to previously-known components whenassessing authenticity of the first application.

Behaviors associated with one or more components of the firstapplication may include, for example, use of personal identifyinginformation or device information, or any actions that can be taken byapplications on the device, including user interface displays,notifications, network communications, and file reading or writingactions. In one embodiment, the evaluating of the first application mayinclude analysis of components of the first application as described inthe section above titled “Analyzing Components of an Application” (andalso further optionally include analysis of components in otherapplications being compared to the first application).

In one embodiment, the first application above is a mobile application,which contains one or more components, such as were discussed previouslyabove. The source of the components is indicated by a componentidentity. In one example, the component identity is an authorship (e.g.,an identification of a developer of the first application), or the nameof a component. Previously collected data associated with a givencomponent may be stored in a database (e.g., as was discussed above).

In one embodiment, as discussed in more detail below, for a firstapplication being installed on mobile device 149, components areidentified and behaviors exhibited on mobile device 149 are attributedto one or more of the components. Any given component may be present inseveral different applications on mobile device 149 and/or may be commonto numerous copies or versions of an application that have beeninstalled on computing devices for large numbers of other users. In oneembodiment, this commonality of component presence permits observing andcollecting structural and behavioral data associated with the component.This known component data is stored in a database (e.g., database 1007discussed above) and the component data is associated with a particularcomponent identity. Thus, a data repository of prior component data canbe used to compare to data more recently obtained for new components(such as those identified in newly-installed applications on a mobiledevice) when evaluating authenticity of the first application beinginstalled.

More specifically, as characteristics and behaviors associated withcomponents on mobile device 149 are identified and attributed, thesecharacteristics and behaviors may be compared with known characteristicsand behaviors stored either locally on mobile device 149 or storedremotely on authenticity server 1005 in database 1007. The results fromsuch comparisons may be used as inputs for the evaluating of the firstapplication being installed (e.g., for making decisions regardingdisabling of one or more particular components that are being consideredfor a new installation on the mobile device).

In one embodiment, behavioral and/or structural characteristics of acomponent present in the first application may be identified (e.g., aswas discussed in the section titled “Analyzing Components of anApplication” above). This may be, for example, an application that isbeing installed on mobile device 149 and for which the user desires todetermine if the application is from an authentic source (e.g., a knowndeveloper of an earlier or related version of the new application).

A comparison is made between the characteristics attributable to acomponent associated with the first package identifier andcharacteristics that have been identified in the new application. In oneembodiment, if the identified characteristics are different from thecharacteristics associated with the first package identifier, then analert is generated to indicate that the new application is notauthentic. The characteristics associated with the first packageidentifier may be stored in a database of authenticity server 1005 andmay be accessed when making this comparison (alternatively, thecharacteristics may be stored in a database and/or the comparison madeor supported by an identity server). For example, these attributablecharacteristics may be stored as component data associated withrespective component identities.

Each component identity has identifying information for a givencomponent that, if present in an application, indicates that the givencomponent is present in the application. Examples of identifyinginformation include the following: a package name prefix for a set ofone or more classes, a class name, or a code fingerprint of a codeblock, method, class, package, etc.

Analysis of a new application being installed can be used to determineif identifying information for a given component identity matches thenew application. If it matches, then the given component is present inthe new application. This analysis can be done at the client (e.g.,mobile device 149), the server (e.g., authenticity server 1005 or anidentity server), or using a combination thereof. This match thatdetermines presence of the component in the new application can be usedas an input in evaluating authenticity of the new application.

In a different embodiment, the client submits an identifier for the newapplication to a server (e.g., authenticity server 1005). Thisidentifier may be, for example, a hash of the application binary code, apackage name, a title of the application, or another form of applicationidentifier. This server stores data regarding previously-analyzedapplications. This data includes data associated with each component ofa set of components for each of the previously-analyzed applications.

The server uses the identifier received from the client and comparesthis identifier to the data regarding previously-analyzed applications.If there is a match between the identifier and a previously-analyzedapplication, then the components for that matched application (obtainedfrom the stored set of component data above) are determined to be in thenew application. This result may be sent to the client. Also, thisresult may be used as one of the plurality of inputs in evaluating theapplication. In one example, this matching is done similarly as wasdescribed earlier above for the component analysis on a single device.The server sends information about these identified component identitiesback to the client (e.g., a notification that a new application is notauthentic, or a score indicating the risk of a fraudulent application).

If the actual behavior and the known behavior for the component identityare different, this may indicate that the component in the newapplication is either a newer version or a tampered-version (i.e., isnot authentic), and that the component needs to be reviewed again inorder to update the database. Also, an alert may be generated based onthe component information determined above. For example, an email may besent to an analyst to do further analysis of a component, or an entrymay be created in a work queue regarding further component analysis tobe done. In another example, a notification is sent to the developer ofa prior, known-good version of an application (e.g., to alert thedeveloper that a fraudulent version of the application was identified).

Yet further additional non-limiting embodiments and examples are nowdiscussed below. In a first embodiment, a developer registers through awebsite and provides its signing key. The developer claims authorship ofa given application. An application that is signed with this key isconsidered to be authored by the developer. If the same application issigned by a different person or entity, then authenticity server 1005alerts the developer that another entity is potentially illegitimate.

In one embodiment, authenticity server 1005 implements an authenticitycomponent and a response component. An application is evaluated by theauthenticity component and the result from the authenticity component isacted upon by the response component.

The authenticity component is a data set that may include a plurality ofinputs used for evaluating an application. For example, these inputs mayinclude that a developer signs an application, the prevalence of anapplication, the context or environment in which the application isobserved, and a history of the signing key or certificate associatedwith an application.

The output from this evaluation may be a score such as, for example, 0.4or 0.6 on a scale of 0.0-1.0. This multi-input authenticity componentmodel provides a result that is acted upon by the response component. Inone embodiment, the score is used to make a decision to set a statedesignation for an application to trusted or untrusted.

Another embodiment is based on probability, in which it is assumed thatthe most popular version of a given application is the legitimate one.Another embodiment assumes that the application that is published inGoogle Play, or another legitimate application store, is the legitimateor authentic one.

If another version of that same application is signed by a differentperson, then one of the applications is authoritative and the other isnot. Authenticity server 1005 alerts the user the mobile device as towhether a version being installed is authentic.

In one embodiment, there are various ways to determine the authenticversion of several versions of an application being distributed. In somecases the most popular version of an application may not be theauthentic version of the application. Thus, a collection of factors areused from the exemplary inputs provided above (e.g., whether theapplication is published in the Google Play store, what is the contextof the observation of the application, does the application have goodonline reviews over an extended predetermined time period, such as forexample more than 6 months, etc.).

In one embodiment, the history of usage of a signature is considered asan input. For example, if a signing key is used to sign an applicationthat authenticity server 1005 knows is bad, then if that same key signsother applications, those applications can also be assumed to be bad.This is like a signer reputation. If the signer is connected to priorsuspicious activity, then the signer itself can be flagged assuspicious, and this fact considered in evaluating authenticity.

Another input may be the signing of different applications thatauthenticity server 1005 knows are provided from different developers.Another input is that the applications may communicate with differentservers in different parts of the world—this indicates that one of theapplications is not authentic and/or that there are potentiallydifferent developers.

In one embodiment, the first appearance of a signed applicationindicates authenticity. For example, the first person to sign andpackage that application is considered or assumed to be the authenticauthor. Authenticity server 1005 may have a huge network of devices(e.g., greater than 10,000 or 1 million devices) that report all theapplications that they see. Therefore, presumably the legitimateapplication appears first as stored in database 1007. For example, thefirst time that the server sees an application, it will take thesignature on that application and consider it to be the authenticsignature.

In one embodiment, another input is the number of stars or other ratinglevel that an application gets in Google Play or another store. Forexample the application may have been in a store for at least apredetermined time period (e.g., at least one or two years) and have agood rating. If the application has at least a predetermined number ofratings, for example, 300,000 ratings, and a star value over a givenlevel, then the application is likely a legitimate version of theapplication.

In one embodiment, the longevity of the key is an input. The longevitymay be a weighted user distribution based on time period and number ofusers. For example, if the application is observed for a year, but withvery little users, that is a negative input. However, in contrast,having a million users over a year is a positive sign.

In one embodiment, various inputs are provided into a black box modelused in authenticity evaluation. The inputs may include, for example,the signing key as registered by the developer itself, the usage historyof a signing key, a history-weighted time of first appearance, anappearance in certain reputable application stores, a signing key usedto sign applications that are substantially different, applications thattalk to substantially different servers, applications that havesubstantially different code bases, and two applications that are signedand appear under different developer names in an authoritativemarketplace such as Google Play.

In one embodiment, there are different interfaces provided for differentusers to provide information from authenticity server 1005 about theresult from the evaluation of the authenticity. For the user (e.g., userof a mobile device), there may just be a warning provided (e.g., a popupthat states that an application is not authentic). An alternative is anotice that indicates (e.g., an authentication seal that appears in thelower right-hand corner of a window) to the user that this is anauthentic application. As one example, a user is presented and sees anauthentication seal when a banking application is being installed by theuser on its mobile device.

CLOSING

In this description, various functions and operations may be describedas being performed by or caused by software code to simplifydescription. However, those skilled in the art will recognize what ismeant by such expressions is that the functions result from execution ofthe code by a processor, such as a microprocessor. Alternatively, or incombination, the functions and operations can be implemented usingspecial purpose circuitry, with or without software instructions, suchas using an Application-Specific Integrated Circuit (ASIC) or aField-Programmable Gate Array (FPGA). Embodiments can be implementedusing hardwired circuitry without software instructions, or incombination with software instructions. Thus, the techniques are limitedneither to any specific combination of hardware circuitry and software,nor to any particular source for the instructions executed by acomputing device.

While some embodiments can be implemented in fully functioning computersand computer systems, various embodiments are capable of beingdistributed as a computing product in a variety of forms and are capableof being applied regardless of the particular type of machine orcomputer-readable media used to actually effect the distribution.

At least some aspects disclosed can be embodied, at least in part, insoftware. That is, the techniques may be carried out in a computingdevice or other system in response to its processor, such as amicroprocessor, executing sequences of instructions contained in amemory, such as ROM, volatile RAM, non-volatile memory, cache or aremote storage device.

Routines executed to implement the embodiments may be implemented aspart of an operating system, middleware, service delivery platform, SDK(Software Development Kit) component, web services, or other specificapplication, component, program, object, module or sequence ofinstructions referred to as “computer programs.” Invocation interfacesto these routines can be exposed to a software development community asan API (Application Programming Interface). The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processors in a computer, cause the computerto perform operations necessary to execute elements involving thevarious aspects.

A machine readable medium can be used to store software and data whichwhen executed by a computing device causes the device to perform variousmethods. The executable software and data may be stored in variousplaces including for example ROM, volatile RAM, non-volatile memoryand/or cache. Portions of this software and/or data may be stored in anyone of these storage devices. Further, the data and instructions can beobtained from centralized servers or peer to peer networks. Differentportions of the data and instructions can be obtained from differentcentralized servers and/or peer to peer networks at different times andin different communication sessions or in a same communication session.The data and instructions can be obtained in entirety prior to theexecution of the applications. Alternatively, portions of the data andinstructions can be obtained dynamically, just in time, when needed forexecution. Thus, it is not required that the data and instructions be ona machine readable medium in entirety at a particular instance of time.

Examples of computer-readable media include but are not limited torecordable and non-recordable type media such as volatile andnon-volatile memory devices, read only memory (ROM), random accessmemory (RAM), flash memory devices, removable disks, magnetic diskstorage media, optical storage media (e.g., Compact Disk Read-OnlyMemory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others.The computer-readable media may store the instructions.

The instructions may also be embodied in digital and analogcommunication links for electrical, optical, acoustical or other formsof propagated signals, such as carrier waves, infrared signals, digitalsignals, etc. However, propagated signals, such as carrier waves,infrared signals, digital signals, etc. are not tangible machinereadable medium and are not configured to store instructions.

In general, a tangible machine readable medium includes any mechanismthat provides (e.g., stores) information in a form accessible by amachine (e.g., a computer, network device, personal digital assistant,manufacturing tool, any device with a set of one or more processors,etc.).

In various embodiments, hardwired circuitry may be used in combinationwith software instructions to implement the techniques. Thus, thetechniques are neither limited to any specific combination of hardwarecircuitry and software nor to any particular source for the instructionsexecuted by a computing device.

Although some of the drawings illustrate a number of operations in aparticular order, operations which are not order dependent may bereordered and other operations may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beapparent to those of ordinary skill in the art and so do not present anexhaustive list of alternatives. Moreover, it should be recognized thatthe stages could be implemented in hardware, firmware, software or anycombination thereof.

In the foregoing specification, the disclosure has been described withreference to specific exemplary embodiments thereof. It will be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope as set forth in the following claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative sense rather than a restrictive sense.

1. A system, comprising: at least one processor; and memory storinginstructions configured to instruct the at least one processor to:receive, from a first computing device, a first application identifierfor a first application; determine a first source identifier of thefirst application; send the first application identifier and the firstsource identifier over a network to a second computing device; receive,from the second computing device, a first state designation for thefirst application, the first state designation representing a trustedstate or an untrusted state; in response to receiving the first statedesignation, set a second state designation; and send the second statedesignation to the first computing device.
 2. The system of claim 1,wherein the first source identifier is determined based on monitoringnetwork activity.
 3. The system of claim 1, wherein the first sourceidentifier is determined by detecting the first source identifier on thefirst computing device.
 4. The system of claim 1, wherein the firstsource identifier is determined by detecting code that operates in thenetwork path from a network source to the first computing device.
 5. Thesystem of claim 4, wherein the code is detected operating in a networkdevice.
 6. The system of claim 1, wherein the first source identifier isan IP address, a domain, or a uniform resource locator.
 7. The system ofclaim 1, wherein: the second computing device is configured to store alist of trusted source identifiers, and to store first data regarding atleast one trusted application for each respective trusted sourceidentifier of the list; and the first state designation is determinedbased on the first data.
 8. The system of claim 1, wherein: the firstcomputing device is configured to use a plurality of install locationsto install applications; the first application is to be installed in afirst install location of the plurality of install locations; and thefirst state designation is determined based on the first installlocation.
 9. The system of claim 1, wherein sending the second statedesignation to the first computing device causes the first computingdevice to set an application state to untrusted.
 10. The system of claim9, wherein the first computing device is configured to, in response toreceiving the second state designation, perform at least one of blockinginstallation of the first application, blocking execution of the firstapplication, disabling execution of one or more components of the firstapplication, denying the first application access to a network, oruninstalling the first application.
 11. The system of claim 1, whereinthe instructions are further configured to instruct the at least oneprocessor to: determine that applications from the first sourceidentifier are untrusted; determine that the first application isidentical to a second application, wherein the second application isdetermined to be from a trusted source; and in response to determiningthat the first application is identical to the second application, setthe second state designation to represent a trusted state.
 12. A method,comprising: receiving a first application identifier for a firstapplication to be installed on a first computing device; determining afirst source identifier of the first application; sending the firstapplication identifier and the first source identifier over a network toa second computing device; receiving, from the second computing device,a first state designation for the first application, the first statedesignation representing a trusted state or an untrusted state; inresponse to receiving the first state designation, setting a secondstate designation; and sending the second state designation to the firstcomputing device.
 13. The method of claim 12, wherein the firstcomputing device stores the first source identifier.
 14. The method ofclaim 12, wherein determining the first source identifier comprisesmonitoring activity for a second application that is associated with thefirst application identifier.
 15. The method of claim 14, whereinmonitoring activity for the second application comprises monitoringnetwork activity on a third computing device.
 16. The method of claim14, wherein monitoring activity for the second application comprisesmonitoring, in a virtual machine, behavior of the second application.17. The method of claim 12, wherein prior to receiving the firstapplication identifier, the first source identifier is determined to betrusted, and wherein the method further comprises: after receiving thefirst application identifier, determining that the first sourceidentifier is untrusted based on behavior associated with the firstsource identifier; and in response to determining that the first sourceidentifier is untrusted, setting the second state designation torepresent an untrusted state.
 18. The method of claim 12, furthercomprising denying, based on the determined first source identifier,access by the first computing device to a network location associatedwith the first source identifier.
 19. The method of claim 18, whereinthe access by the first computing device to the network location isdenied further based on a policy for the first computing device set bythe second computing device.
 20. A non-transitory computer-readablestorage medium storing computer-readable instructions, which whenexecuted, cause a first computing device to: receive, from a secondcomputing device, a first application identifier for a firstapplication; determine a first source identifier of the firstapplication; send the first application identifier and the first sourceidentifier over a network to a third computing device; receive, from thethird computing device, a first state designation for the firstapplication, the first state designation representing a trusted state oran untrusted state; in response to receiving the first statedesignation, set a second state designation; and send the second statedesignation to the second computing device.